VirusTotal
11 / 89
As of 2026-10-01, ammyield.com returned an HTTP status code 502 in the recorded HTTP check. The same evidence set records a first observation date of 2026-09-02 for this domain.
The domain ammyield.com appears on two external blocklists, MetaMask and SEAL, per the blocklist check dated 2026-10-01. VirusTotal recorded 11 detections across 89 scanners on 2026-09-13. OTX recorded 2 pulses on 2026-09-13. The registrar listed in the evidence is Gname.com Pte. Ltd.
MetaMask, SEAL, VirusTotal and OTX were observed on different dates, so their records describe separate points in time rather than one synchronized snapshot. Because the HTTP check and the blocklist check share the 2026-10-01 date while VirusTotal and OTX carry the 2026-09-13 date, a reader can compare the two dates but cannot treat any single record as current. The 502 response is a recorded status at that time, not a statement about present availability.
Retain the existing records for ammyield.com, including the dated HTTP, blocklist, VirusTotal and OTX observations, so later checks can be compared against them. When reviewing ammyield.com again, note the date of each new observation and compare it with the earlier dates rather than merging them. Avoid submitting sensitive information during any review of ammyield.com until the recorded status is better understood.
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='ammyield.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