VirusTotal
checked — no detections recorded
“DappsTools”
On 2026-10-01, projectsdapps.pages.dev returned an HTTP 403 status code according to a recorded HTTP check. The same source set records a first observation date of 2026-09-13 for this domain. A PhishDestroy internal listing is also recorded, and VirusTotal reported 0 detections across 89 scanners on 2026-09-19.
The HTTP check dated 2026-10-01 recorded status 403, while the SSL scan dated 2026-09-19 named Google Trust Services / WE1 as issuer. VirusTotal, checked on 2026-09-19, recorded 0 detections out of 89 scanners. The PhishDestroy internal listing and the first observation dated 2026-09-13 complete the recorded set.
The dated HTTP response describes only the reply recorded at that check, not the domain's content or present availability. The PhishDestroy catalogue entry and the VirusTotal result are separate source observations, and their differing dates and metrics do not establish a trend. The first observation date marks when the domain entered these records, not when it was created.
Preserve the HTTP check, the VirusTotal result, the PhishDestroy internal listing, and the first observation record for projectsdapps.pages.dev. Compare the HTTP record and the VirusTotal record separately in later reviews, since each measures a different thing. Avoid submitting credentials or personal information to projectsdapps.pages.dev while these records remain the basis for review.
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.
97bf35e13419ba6e6b9ac43059b371c00d5df7240c404f6851a893cb9eba4b9dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
5 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