VirusTotal
11 / 89
On 2026-10-01, ammhubs.com returned an HTTP 502 status in a recorded check, a server-side error at that moment. The domain was first observed on 2026-09-02, and a PhishDestroy internal listing is also recorded.
An external blocklist check on 2026-10-01 lists ammhubs.com with MetaMask, ScamSniffer, and SEAL. VirusTotal recorded 11 detections across 89 scanners on 2026-09-13. OTX recorded two pulses on 2026-09-13. The registrar was recorded as Gname.com Pte. Ltd.
The MetaMask, ScamSniffer, and SEAL listings, the VirusTotal and OTX results, and the HTTP check carry different observation dates, so each reflects only its own collection moment. Because those dates differ, a reader can compare them as separate records rather than treating them as one simultaneous snapshot. The 2026-09-02 first observation predates the later checks, which affects how the sequence of records can be read.
Retain the dated records for ammhubs.com, including the blocklist entries, VirusTotal and OTX results, and the HTTP response, so later checks can be compared against them. When reviewing ammhubs.com, avoid submitting sensitive or personal information, and note the date of each new observation. Comparing subsequent records with these earlier dates helps show whether the recorded status has changed.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ammhubs.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
patrick.ns.cloudflare.comLocation describes the IP network.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
79 stored lookalike domains
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive