VirusTotal
3 / 90
“Site Not Found | Framer”
metamaskcdn-us.framer.website returned HTTP status 404 in a check recorded on 2026-10-01. The same domain was first observed on 2026-09-17, according to the recorded timeline.
A VirusTotal check dated 2026-09-23 recorded 3 detections across 90 scanners. The external blocklists MetaMask and SEAL both listed the domain, and the PhishDestroy internal listing was also recorded. An SSL scan dated 2026-09-21 named the issuer as Let's Encrypt / YE1, while the resolved IP 31.43.161.6 was attributed to Framer B.V in NL. The blocklist check was dated 2026-10-01, matching the HTTP check date.
The recorded sources describe different aspects of the same domain rather than a single confirmed condition. The HTTP 404 response reflects only the response captured on that date, and the blocklist entries reflect listings by MetaMask and SEAL at the time of their checks. Because the first observation, SSL scan, VirusTotal check and HTTP check fall on different dates, the records can be compared chronologically without treating any single date as a complete picture. The VirusTotal detections and the blocklist listings are separate measurements and should not be merged into one conclusion.
Preserve the HTTP response record for metamaskcdn-us.framer.website and the blocklist entries from MetaMask and SEAL as separate source records. Compare the VirusTotal detection record with the PhishDestroy internal listing in separate sentences when reviewing the domain. Retain the first-observed entry and the SSL scan record for later comparison against future checks of metamaskcdn-us.framer.website.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Framer/26fa766Scanner note: hosting_placeholder: raw=placeholder; http=404; via=https_proxy; server=Framer/26fa766
ns-792.awsdns-35.netLocation describes the IP network.
c1bcfe2b693839624953b2dc076fc7edc64f3e310c88b51701c5868fff6d9a26Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 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