VirusTotal
7 / 89
As recorded on 2026-10-01, airdrop-x.com appeared on the external blocklists MetaMask and SEAL. The same domain also carries a PhishDestroy internal listing, and its first observation is dated 2026-08-31.
VirusTotal, checked on 2026-09-13, reported 7 detections across 89 scanners. OTX, checked on 2026-09-13, recorded 2 pulses for the domain. The external blocklist count of 2 was recorded on 2026-10-01, naming MetaMask and SEAL. PhishDestroy holds an internal listing for airdrop-x.com, and the first observed date is 2026-08-31.
The MetaMask and SEAL blocklist entries carry a later date than the VirusTotal and OTX checks, so the sources describe different moments and cannot be treated as one snapshot. Because OTX and VirusTotal share the 2026-09-13 check date, their records can be compared directly, while the 2026-08-31 first observation and the 2026-10-01 blocklist date sit outside that pairing. Each named source contributes a separate dated reference point for review.
Retain the dated records for airdrop-x.com so later checks can be compared against the 2026-08-31, 2026-09-13, and 2026-10-01 observations. During review of airdrop-x.com, avoid submitting sensitive information and rely on the named sources when noting changes.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='airdrop-x.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(
leif.ns.cloudflare.comLocation describes the IP network.
9 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.
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