VirusTotal
15 / 89
“Suspected Phishing | Cloudflare”
42cr2c32.pages.dev returned HTTP status 403 in a response recorded on 2026-10-01, the most recent HTTP observation in this evidence set. The same domain was first observed on 2026-08-05, according to the recorded first-observation date.
Google Safe Browsing flagged the domain for social engineering on 2026-09-14, and VirusTotal recorded 15 detections across 89 scanners on the same date. An SSL scan on 2026-09-13 identified the issuer as Google Trust Services / WE1, while the HTTP check on 2026-10-01 returned status 403. The domain resolves to 172.66.44.52, associated with Cloudflare, Inc. in CA, and it appears in the PhishDestroy internal listing.
Safe Browsing and VirusTotal are independent source records, so their shared calendar date does not establish simultaneous measurement or direct comparability. The HTTP 403 describes only the recorded response, not all content that may exist on the domain. The chronology from first observation to the later checks is useful for ordering records, but the dates alone do not demonstrate a change in behavior.
Preserve the Safe Browsing, VirusTotal, SSL, and HTTP records for 42cr2c32.pages.dev as separate source artifacts. Compare the Safe Browsing flag against the VirusTotal detections in separate sentences rather than merging them into one verdict. Retain the PhishDestroy listing entry alongside the dated HTTP response for future reference.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
6189ddf6a27c5d758c207cf2ef901a0f6a8307ec24a04ff75efb3d12361c3d9cSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
142 stored lookalike domains
Showing 100 of 142
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive