VirusTotal
4 / 89
“Site Not Found | Framer”
On 2026-10-01, apps-rabby.framer.website returned HTTP status 404, a dated response recorded during an HTTP check. The domain was first observed on 2026-09-17, roughly two weeks before that check.
The domain appears on two external blocklists, MetaMask and SEAL, and also has a phishdestroy internal listing. VirusTotal recorded 4 detections across 89 scanners on 2026-09-23, while the SSL certificate, issued by Let's Encrypt / YE1, was scanned on 2026-09-21. The IP address 31.43.161.6 is associated with Framer B.V in NL, and the external blocklist check occurred on 2026-10-01.
The MetaMask and SEAL listings, the phishdestroy internal listing, and the VirusTotal result reflect observations made on different dates, so their counts and statuses describe separate snapshots rather than one synchronized measurement. Because the HTTP 404 was recorded on 2026-10-01 and the SSL scan on 2026-09-21, a reader can compare these dated records but cannot treat either as a current statement about the domain.
Reviewers should retain the dated records for apps-rabby.framer.website, including the HTTP 404 and the blocklist entries, so later observations can be compared against them. Any follow-up check should be logged with its own date, and reviewers should avoid submitting sensitive information while examining apps-rabby.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.
20 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