SiteReport is the public-facing intake of 78 OVER 37 LIMITED. Send us a suspicious URL — phishing, fake shop, fraudulent investment, malware download, impersonation — and we'll investigate, capture evidence and initiate the takedown with the host, registrar and browser safe-browsing partners.
Fake login pages for banks, postal services, government portals, social platforms or wallets. The page asks you to enter credentials, a one-time code, a card number or a seed phrase, and forwards them to the operator.
Sites selling discounted electronics, designer goods, medications or limited-edition items that never arrive — typically on a freshly registered domain with stolen product photography and fake review widgets.
Cloned trading platforms, "AI" investment dashboards, fake exchange withdrawal pages, romance-investment funnels, fraudulent ICOs and rug-pull token sites with cloned whitepapers.
Sites pushing fake "browser updates", cracked-software bundles, drainer wallets, info-stealers or remote-access trojans. We coordinate with browser safe-browsing partners and antivirus vendors for blocking.
Look-alike domains pretending to be a real company's customer-support page, refund portal, tax page or shipping tracker. Often paired with a smishing or social-media advert that pushes traffic to the fake site.
Sites publishing fabricated allegations against an individual, sextortion landing pages, ransom payment portals, or "review" sites built to extort a removal fee from the listed business.
Within the first hour we usually have browser-level safe-browsing partners showing this warning to anyone who clicks the abuser's smishing or social-ad bait.
By form, email or Telegram bot. Attach any screenshots, the original SMS or email, and the brand or person being impersonated. You'll receive an automatic acknowledgement and a case number.
An analyst confirms the abuse vector, identifies the host, registrar, certificate issuer and (where applicable) the payment processor. Critical phishing is fast-tracked into the safe-browsing block channels first.
Time-anchored screenshots, source HTML, redirection chains, DNS, WHOIS and certificate transparency are hashed and stored in immutable archives so the case is admissible if it ever needs to escalate.
We contact the host, the registrar, the registry, browser safe-browsing partners and (when relevant) ad networks at the same time. Speed matters: a campaign that lives an extra two hours can claim hundreds more victims.
Most operators have rehost infrastructure ready. We track new hosting, new domains and new IP ranges, and re-engage abuse channels until the campaign is no longer economical.
If you provided an email when reporting, we send a closure note: when the site went dark, where it tried to rehost, and what to watch for if you see a similar pattern again.
You don't need to figure out who hosts the site, which registrar to write to, or how to draft an abuse complaint that actually triggers action. We've done it tens of thousands of times. We know which abuse desks need a screenshot vs source HTML vs a notarised affidavit, and we send the right pack first time.
We hash, time-anchor and chain-of-custody every artefact. If the case ever has to escalate to law enforcement, a UDRP-adjacent dispute or a defamation claim, you don't lose the evidence to a deletion or a CDN cache flush.
We do not pass reporter identity to the operator of the abusive site. Hosts and registrars receive only the evidence they need to act. Your email is used only to send a case number and a closure note unless you explicitly ask for more contact.
SiteReport is operated by the same team behind Overload.su's domain-takedown practice — a paid B2B service for major brands. The intake here is the consumer-facing entry point with the same closure standard.
Use the report form on this page, email support@overload.su, or message @OverSupBot on Telegram. Include the full URL, screenshots if you have them, the original SMS or email that pointed you at the site, and the brand or person being impersonated. We acknowledge every submission with a case number and triage within hours.
Yes — for individual victims and one-off consumer reports it is always free. We absorb the cost as part of our public-service intake, and recover it on the brand-owner side through retainers and case management. If you are a brand owner with ongoing monitoring needs we'll quote a retainer separately.
At a minimum: the full URL (don't trim parameters; they can identify the campaign). Ideally: a screenshot of the page, the email or SMS that referred you to the site, and the brand the operator is impersonating. If money has been lost or credentials entered, also report this to your bank, your country's CERT and your local police; we'll cooperate with their investigators on request.
For clear phishing on compliant hosts, browser-level blocking via safe-browsing partners typically lands within 33 minutes; full host-level removal within 24 hours. Less responsive hosts and offshore registrars can extend the timeline to several days. Some campaigns operate from non-cooperating jurisdictions; in those cases we focus on browser blocking, payment-processor disruption and ad-network removal as the practical end-game.
No. We do not share reporter identity with the abusive operator. We share only the evidence required by the host or registrar to act, and we redact reporter details by default unless you tell us we may include them.
The site itself, yes. The SMS sender, partly: we coordinate with mobile-operator abuse desks and the URL-shortener provider in the message, but SMS-level blocking ultimately depends on the carrier. If you can forward the original SMS (with header information), we will include it in the case file.
Yes. Defamation cases need slightly different evidence: the page content, the date of publication, why the statements are false and (where relevant) any proof of harm. We will tell you which evidence we still need after intake.
You can submit phishing pages directly to Google Safe Browsing at safebrowsing.google.com. We file Google Safe Browsing reports as part of our standard workflow, but reporting a critical phishing page to multiple channels in parallel never hurts.