mage-glade-44.pages.dev returned HTTP status 403 in an HTTP check dated 2026-10-01, the most recent recorded response for this hostname. The same evidence set also records a PhishDestroy internal listing, first observed on 2026-09-13.
Recorded Evidence
An HTTP check dated 2026-10-01 recorded status 403 for mage-glade-44.pages.dev. The PhishDestroy internal listing was first observed on 2026-09-13. A VirusTotal scan dated 2026-09-19 reported 0 detections across 89 scanners. An SSL scan dated 2026-09-19 identified the issuer as Google Trust Services / WE1. The IP address 188.114.96.9 is recorded with country CA and organization CloudFlare, Inc.
Interpretation
The PhishDestroy listing and the HTTP response are separate records with different dates, so they describe distinct observations rather than a single measurement. The 0-of-89 VirusTotal result and the 403 response come from different sources and dates, so they cannot be combined into one conclusion. The chronology from first observation on 2026-09-13 to the later checks shows only that records were collected at different times, not that conditions changed.
Recommended Actions
Review the PhishDestroy internal listing and the recorded HTTP response for mage-glade-44.pages.dev, and preserve both source records for later comparison. Compare the VirusTotal scan result with the HTTP check in separate reviews rather than merging them. Re-check the domain's HTTP response and the PhishDestroy listing at a later date to see whether the recorded observations remain consistent.
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-13 14:28:07 UTCcurrent episode first observed: 2026-10-01 01:53:12 UTCobserved RIP window: 2026-09-13 14:28:07 UTC → 2026-10-01 01:53:12 UTC · 419.42hmidpoint estimate ≈ 2026-09-22 08:10:39 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.
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-19 22:00:27 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 18:23:49 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
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)
