VirusTotal
10 / 89
On 2026-10-01, ammswapx.com returned an HTTP 502 status code during a recorded check, indicating a server-side response at that time. The domain was also first observed on 2026-09-02, providing a reference point for its earliest recorded activity.
A blocklist check on 2026-10-01 found ammswapx.com listed on MetaMask and SEAL external blocklists. VirusTotal, as checked on 2026-09-13, reported 10 detections out of 89 scanners for the domain. OTX, checked on 2026-09-13, recorded 2 pulses associated with ammswapx.com. The domain is also present on the phishdestroy internal listing, and its registrar is Gname.com Pte. Ltd.
The HTTP 502 status code is limited to the specific check on 2026-10-01 and does not indicate ongoing content or availability. The MetaMask and SEAL blocklist entries, as well as the phishdestroy internal listing, are separate records that each flag the domain in their respective systems. VirusTotal and OTX provide independent observations, and their figures should be considered distinct from one another. The range of source dates reflects multiple checks but does not establish any timeline of changes.
Retain the HTTP status record and blocklist findings for ammswapx.com as individual source references. Review MetaMask, SEAL, and phishdestroy listings separately for further context. Preserve the VirusTotal and OTX records for future comparison with new observations. Avoid submitting sensitive information to ammswapx.com based on the recorded evidence.
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='ammswapx.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
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