On 2026-10-01, trazor-io-guide-info.netlify.app returned HTTP status 404, so the requested resource was not available in that recorded response. The domain was first observed on 2026-09-03, and a PhishDestroy internal listing was recorded as present.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for trazor-io-guide-info.netlify.app. VirusTotal, checked on 2026-09-14, reported 12 detections across 89 scanners. The SSL scan on 2026-09-14 named DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 as issuer. The domain resolved to IP address 35.157.26.135, with AWS EC2 (eu-central-1) as the recorded organization in DE. PageSpeed on 2026-09-14 recorded a performance score of 100.
Interpretation
The HTTP 404 record describes only the response captured on that date, not all content the domain may have served. The VirusTotal detection count reflects scanner output at its own check time, while the PhishDestroy listing is a publisher-owned catalogue entry. Because these observations fall on different dates, they should be compared as separate records rather than treated as a single trend.
Recommended Actions
For trazor-io-guide-info.netlify.app, preserve the HTTP status record and the VirusTotal detection report as separate source documents. Compare the PhishDestroy listing against those records when reviewing the domain's history. Retain the PageSpeed and SSL scan outputs alongside them for future reference. Recheck the domain periodically and archive each new observation with its source name.
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 Unavailability11 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 3, 2026
Favicon Hash
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
35.157.26.135
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:40 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-03 17:28:09 UTCcurrent episode first observed: 2026-10-01 01:39:22 UTCobserved RIP window: 2026-09-03 17:28:09 UTC → 2026-10-01 01:39:22 UTC · 656.19hmidpoint estimate ≈ 2026-09-17 09:33:45 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.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Fortinet
G-Data
Lionic
Netcraft
PhishFort
Sophos
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of trazor-io-guide-info.netlify.app· checked Sep 14, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
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-14 22:00:17 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-14 10:03:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
trazor-io-guide-info.netlify.app detected and queued for full analysis
Sep 3, 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 15, 2026
Time to First Unavailability
269 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 →
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)
