Security engines reporting a detection: 13. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, leaderboardstatusvote-ux.netlify.app returned HTTP status 404, a dated response recorded during an HTTP check. The same hostname was first observed on 2026-08-31, according to the recorded first observation date.
Recorded Evidence
The domain leaderboardstatusvote-ux.netlify.app was first observed on 2026-08-31, and its HTTP status was recorded as 404 on 2026-10-01. A PageSpeed check on 2026-08-31 produced a performance score of 62. An SSL scan on 2026-08-31 identified the issuer as DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1. VirusTotal, checked on 2026-09-14, reported 13 detections across 89 scanners. External blocklists MetaMask and SEAL were recorded, with the blocklist check dated 2026-10-01. The internal PhishDestroy listing was recorded as true.
Interpretation
The HTTP 404 response dated 2026-10-01 and the first observation dated 2026-08-31 come from different checks, so they describe separate moments rather than one continuous state. The VirusTotal result dated 2026-09-14 and the external blocklist entries dated 2026-10-01 were also collected on different dates, which limits direct comparison across sources. The PageSpeed and SSL observations dated 2026-08-31 predate the later checks, so their values reflect an earlier point in the record.
Recommended Actions
Anyone reviewing leaderboardstatusvote-ux.netlify.app should retain the dated observations, including the 2026-10-01 HTTP check and the 2026-08-31 first observation, so later comparisons use the same reference points. Subsequent checks of leaderboardstatusvote-ux.netlify.app can be compared against the recorded HTTP status, blocklist entries and VirusTotal result to see whether the records change over time. During review, avoid submitting sensitive information to the domain until the recorded observations have been independently verified.
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.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
BIBI Price Today | Live BIBI Price, Chart & Market Data
Impersonates
Binance
TLS Certificate
Certificate hostname mismatch·
Issued by DigiCert Inc· stored validity ends in 198 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
63.176.8.218
Network ASN
AS16509
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt am Main, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
DigiCert Inc
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-31 10:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478Certificate names · 1 SANs
netlify.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-11 01:14:32 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-11 01:19:46 UTCcurrent episode first observed: 2026-10-01 01:39:17 UTCobserved RIP window: 2026-09-11 01:19:46 UTC → 2026-10-01 01:39:17 UTC · 480.33hmidpoint estimate ≈ 2026-09-21 01:29:31 UTC · precision low · basis bounded
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
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Google PageSpeed Insights — mobile performance audit of leaderboardstatusvote-ux.netlify.app· checked Aug 31, 2026
62
Needs Work
Performance
FCP
3.3s
First Contentful Paint
LCP
3.53s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
968ms
Total Blocking Time
SI
3.3s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-09-11 16:24:25 UTC
VirusTotal scanner detections updated from 10 to 13. Added scanner alerts: LevelBlue, Lionic, Webroot.
Domain Status Transition2026-09-11 10:09:44 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-08-31 07:31:30 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 63.176.8.218.
Threat Response Pipeline
Discovery
Analysis
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
leaderboardstatusvote-ux.netlify.app 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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 11, 2026
Time to First Unavailability
266 hours elapsed from detection to the first unavailable 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.
3 evidence signal groups linked0 reports recordedContent unavailable
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 matches6
Same favicon hash or the same page title as this host.
(US)
