The domain facebook-verification-badge.com returned HTTP status 404 on 2026-10-01, according to the recorded HTTP check. Separately, the domain was first observed on 2026-09-06, and its registration date is listed as 2026-06-23.
Recorded Evidence
The VirusTotal scan on 2026-09-17 recorded 17 detections across 89 scanners. OTX showed 4 pulses on 2026-09-17, while the PhishDestroy internal listing was recorded as present. The SSL certificate, issued by Let's Encrypt / YR1, was scanned on 2026-09-16, and the registrar is Name.com, Inc. The IP address 64.29.17.65 is associated with Vercel, Inc. in the US.
Interpretation
The VirusTotal and OTX observations share the 2026-09-17 date, while the SSL scan and first observation fall on different dates, so these records reflect separate points in time rather than a single snapshot. The PhishDestroy listing and the HTTP check on 2026-10-01 also come from different dates, meaning the recorded statuses cannot be directly aligned. Comparing these dated sources shows variation in when each was collected, which affects how consistently they can be read together.
Recommended Actions
For facebook-verification-badge.com, retain the dated records from VirusTotal, OTX, and the HTTP check so later observations can be compared against them. When reviewing the domain, avoid submitting sensitive information through any page associated with it until the recorded status is clarified. Subsequent checks should be logged with their exact dates to keep the comparison consistent.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-11 22:05:54 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 22:05:54 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 17 detections
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-15 22:17:56 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-15 10:00:21 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 08:53:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
facebook-verification-badge.com detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
4 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches8
Same favicon hash or the same page title as this host.
(SE)
