Security engines reporting a detection: 3. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
The domain crypto-2rh.netlify.app returned HTTP status 404 on 2026-10-01, a dated response that describes only that recorded request. A separate check on 2026-09-08 recorded a PageSpeed performance score of 100, and the domain was first observed on 2026-09-08.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404, and the domain resolved to IP address 63.176.8.218 in DE under AWS EC2 (eu-central-1). VirusTotal recorded 3 detections across 89 scanners on 2026-09-16, while the external blocklists MetaMask and SEAL were checked on 2026-10-01. The SSL certificate scanned on 2026-09-08 was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1, and the PageSpeed check on 2026-09-08 recorded a performance score of 100.
Interpretation
The named source records describe different measurements taken on different dates, so the HTTP status, blocklist listings, scanner detections and performance score should be read as separate observations rather than a combined verdict. The 2026-09-08 observations and the 2026-10-01 observations are close in time but do not establish a trend on their own. The external blocklist entries and the VirusTotal detections come from distinct sources with distinct methods, so their counts are not directly comparable.
Recommended Actions
Preserve the crypto-2rh.netlify.app HTTP response record and the external blocklist records from MetaMask and SEAL as separate artifacts for later comparison. Compare the VirusTotal scanner results with the PageSpeed performance record in separate reviews, since each source measures a different property. Retain the first-observed and SSL scan records alongside the HTTP and blocklist records so future checks can be compared against the same set of dated observations.
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.
Technical detailsProvenance & timestamps
First DetectedSep 8, 2026
Submitted URLhttp://crypto-2rh.netlify.app/
Favicon Hash
TLS Certificate
Certificate hostname mismatch·
Issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1· stored validity ends in 159 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, 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:14:25 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-08 18:50:39 UTCcurrent episode first observed: 2026-10-01 01:38:58 UTCobserved RIP window: 2026-09-08 18:50:39 UTC → 2026-10-01 01:38:58 UTC · 534.81hmidpoint estimate ≈ 2026-09-19 22:14:48 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 · 4 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of crypto-2rh.netlify.app· checked Sep 8, 2026
100
Good
Performance
FCP
0.75s
First Contentful Paint
LCP
0.75s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.23s
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.
Domain Status Transition2026-09-10 22:04:46 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-10 21:57:50 UTC
VirusTotal scanner detections updated from 0 to 3. Added scanner alerts: Forcepoint ThreatSeeker, VIPRE, alphaMountain.ai.
Threat First Observed2026-09-08 18:50:39 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 63.176.8.218.
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
crypto-2rh.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
51 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 →
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 · crypto-2rh.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.
Content matches4
Same favicon hash or the same page title as this host.
(US)
