VirusTotal
3 / 89
“Demo Protocol – Demo Protocol”
On 2026-10-01, redirectsolutionprotocol.pages.dev returned an HTTP 403 response, a recorded status for that check date. The same domain appears in the phishdestroy internal listing, a separate recorded source.
The domain redirectsolutionprotocol.pages.dev was first observed on 2026-09-07. An external blocklist check on 2026-10-01 recorded one listing, named ScamSniffer. VirusTotal, checked on 2026-09-17, reported 3 detections across 89 scanners. The SSL scan on 2026-09-15 recorded the issuer as Google Trust Services / WE1.
The ScamSniffer listing and the phishdestroy internal listing are separate source records that a reader can compare rather than merge. The HTTP 403 response describes only the response recorded on its check date, not all content served by the domain. Because the first observation and the blocklist check carry different dates, the chronology shows when each record was captured, not a sequence of events.
Preserve the ScamSniffer listing and the phishdestroy internal listing as separate records for later comparison. Compare the VirusTotal result with the external blocklist record in separate sentences when reviewing redirectsolutionprotocol.pages.dev. Retain the HTTP response record alongside those sources so each dated observation remains traceable.
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.
0692967d4c7d6cdb1d022ff4945930c103a4c33656bedb39988e0c07f232807cSaved 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.
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