A request to 344v34v5453.pages.dev on 2026-10-01 returned HTTP status 403, according to the recorded HTTP check. Google Safe Browsing separately flagged the domain for social engineering on 2026-09-14. The full domain 344v34v5453.pages.dev therefore appears in two independent dated records covering different observation types.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 403 for 344v34v5453.pages.dev. Google Safe Browsing, checked on 2026-09-14, flagged the domain with a social engineering threat. VirusTotal, also checked on 2026-09-14, reported 12 detections across 89 scanners. The PhishDestroy internal listing records the domain as listed. The SSL scan on 2026-09-13 identified Google Trust Services / WE1 as the certificate issuer.
Interpretation
The HTTP 403 response and the Safe Browsing social engineering flag describe different kinds of records, so neither should be read as confirming the other. The VirusTotal detection count reflects scanner outputs on its own check date, while the PhishDestroy listing reflects a separate catalogue entry. Because the Safe Browsing and VirusTotal checks share a calendar date, that alone does not establish simultaneous measurement or direct comparability. The HTTP check and SSL scan fall on different dates, which does not by itself demonstrate any change in the domain.
Recommended Actions
Preserve the HTTP check record for 344v34v5453.pages.dev and the Safe Browsing flag as separate source records, since they document different observation types. Compare the VirusTotal detection record against the PhishDestroy listing entry to see whether the two catalogues describe the same domain state. Retain the SSL scan record alongside these sources for future reference. Treat any review of 344v34v5453.pages.dev as requiring consultation of each named source on its own terms.
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.
Provider response during scan: cloudflare_phishing_interstitial
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
Google Safe BrowsingFlaggedSocial engineeringchecked Sep 14, 2026
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerCloudflare Pages
HTTP Status403 Forbidden
Elapsed Since First Report39 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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 DetectedAug 5, 2026
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-12 20:11:38 UTCcurrent episode first observed: 2026-10-01 01:00:42 UTCobserved RIP window: 2026-09-12 20:11:38 UTC → 2026-10-01 01:00:42 UTC · 436.82hmidpoint estimate ≈ 2026-09-21 22:36:10 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 · 3 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 12 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Lionic
Sophos
VIPRE
Webroot
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-12 23:04:53 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-12 19:10:12 UTC
Telemetry event observed.
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
344v34v5453.pages.dev detected and queued for full analysis
Aug 5, 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 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.
1 evidence signal groups linked0 reports recordedReachable · access restricted
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 · 344v34v5453.pages.dev
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.
