Security engines reporting a detection: 9. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-01, usdt-claim.netlify.app returned an HTTP 404 status code during a recorded check, a response tied to that specific request. The same domain was first observed on 2026-09-10, according to the recorded observation history.
Recorded Evidence
The domain was first observed on 2026-09-10. An HTTP status 404 was recorded on 2026-10-01. VirusTotal reported 9 detections out of 89 scanners on 2026-09-20. ScamSniffer included the domain on its blocklist as of 2026-10-02. PhishDestroy recorded an internal listing for the domain. An SSL scan on 2026-09-18 showed the certificate issuer as DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1.
Interpretation
The ScamSniffer blocklist entry and the PhishDestroy internal listing are separate records that can be compared with the HTTP and VirusTotal observations. Because the recorded dates differ, the sources describe distinct points in time rather than a single measurement. The 404 status describes only the response to the request made on that date, not the domain's content or activity at other times.
Recommended Actions
For usdt-claim.netlify.app, retain the ScamSniffer and PhishDestroy listings as distinct records for future reference. Preserve the VirusTotal detection data and compare it with the blocklist entries to monitor changes over time. Recheck the domain's HTTP response and blocklist status using the same sources.
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.
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
IP ContextNetlify shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerNetlify(US)
HTTP Status404 Not Found
Time to First Unavailability12 days
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.
Technical detailsProvenance & timestamps
First DetectedSep 10, 2026
Favicon Hash
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, DE
Server header
Netlify
Edge-IP reputation is not attributed to this domain.
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:32:27 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-29 10:05:48 UTCcurrent episode first observed: 2026-10-01 01:57:50 UTCobserved RIP window: 2026-09-29 10:05:48 UTC → 2026-10-01 01:57:50 UTC · 39.87hmidpoint estimate ≈ 2026-09-30 06:01:49 UTC · precision medium · 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.
Last analyzed First positive detection Previous stored snapshot: 9 detections
alphaMountain.ai
BitDefender
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
PhishFort
Sophos
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-29 22:05:17 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-29 01:00:29 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-26 10:04:23 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-22 22:01:01 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-18 16:33:13 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
usdt-claim.netlify.app detected and queued for full analysis
Sep 10, 2026
Cloudflare Radar Report
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 30, 2026
Time to First Unavailability
293 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.
1 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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · usdt-claim.netlify.app
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.
(US)
