newmultlcrypt.pages.dev returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. The same domain was first observed on 2026-09-06, and it appears on two external blocklists, ScamSniffer and Enkrypt.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 403 for newmultlcrypt.pages.dev. The domain was first observed on 2026-09-06. External blocklist checks on 2026-10-01 listed it on ScamSniffer and Enkrypt. VirusTotal on 2026-09-17 recorded 5 detections across 89 scanners. An SSL scan on 2026-09-15 recorded the certificate issuer as Google Trust Services / WE1. The IP address 172.66.45.46 is associated with Cloudflare, Inc. in CA.
Interpretation
The ScamSniffer and Enkrypt listings and the VirusTotal detections are separate source records, each with its own measurement date, so they should be read as distinct observations rather than combined into a single score. The first-observed date and the later HTTP check show a sequence of recorded events, but the gap between them does not by itself establish any change in the domain's behavior. The 403 response describes only the response recorded on that date, not all content that may be served.
Recommended Actions
Preserve the ScamSniffer and Enkrypt blocklist records for newmultlcrypt.pages.dev, and keep the VirusTotal record alongside them for later comparison. Compare the blocklist records with the HTTP check and the first-observed entry as separate sources, since each carries its own measurement context. Review newmultlcrypt.pages.dev against these saved records before deciding on any further handling.
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-15 22:00:17 UTCcurrent episode first observed: 2026-10-01 01:39:30 UTCobserved RIP window: 2026-09-15 22:00:17 UTC → 2026-10-01 01:39:30 UTC · 363.65hmidpoint estimate ≈ 2026-09-23 11:49:53 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.
技术 · 9 identified
B
Bootstrap
UI frameworks
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS and JavaScript-based design templates for typography, forms, buttons, navigation, and other interface components.
JSDelivr is a free public CDN for open-source projects. It can serve web files directly from the npm registry and GitHub repositories without any configuration.
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: 5 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
VIPRE
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-16 10:00:33 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 10:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(US)
