VirusTotal
7 / 89
“Site Under Maintenance”
On 2026-10-01, justfoethenevent.com returned an HTTP 502 response, indicating an unsuccessful connection at that time. The domain was also listed on two external blocklists, MetaMask and SEAL, according to the same day's blocklist check.
The first recorded observation of the domain was on 2026-08-31. On 2026-09-10, VirusTotal reported 7 detections out of 89 scanners for justfoethenevent.com. OTX also noted 3 pulses for the domain on 2026-09-10. The domain appeared on the MetaMask and SEAL blocklists as of 2026-10-01.
The records from VirusTotal and OTX both reflect observations made on 2026-09-10, while the HTTP status and blocklist listings are from 2026-10-01. These different dates mean each source provides a separate point of reference, allowing for comparison of changes or persistence of findings over time.
Preserve all dated evidence for justfoethenevent.com, including blocklist appearances and scanner results, to enable accurate future reviews. When conducting further checks, compare new findings to these records and avoid entering any sensitive information on the domain during assessment.
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='justfoethenevent.com', port=80): Max retries exceeded with url: / (Caused by NewConnection
thaddeus.ns.cloudflare.comLocation describes the IP network.
Saved 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.
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