On 2026-10-01, sir-frotscher.github.io returned HTTP status 404 in a recorded check, meaning that specific request found no response content. The domain was first observed on 2026-09-11, and a PhishDestroy internal listing is recorded as true.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for sir-frotscher.github.io. VirusTotal on 2026-09-11 recorded 13 detections across 89 scanners. A PageSpeed check on 2026-09-11 recorded a performance score of 100. The domain was first observed on 2026-09-11, and the IP address 185.199.111.153 is recorded in the United States with organization GitHub, Inc. The PhishDestroy internal listing is recorded as true.
Interpretation
The 404 response describes only the outcome of one dated HTTP request, not the full content or current state of the domain. The VirusTotal detection count and scanner total describe a single dated scan, while the PageSpeed score describes a separate dated measurement; these metrics should be read individually rather than combined. The first-observed date and the HTTP check date are distinct records, so the chronology shows when observations were captured rather than proving a change in behavior.
Recommended Actions
Preserve the 2026-10-01 HTTP record and the PhishDestroy internal listing for sir-frotscher.github.io, and compare them with the VirusTotal and PageSpeed records from 2026-09-11. Review the recorded HTTP status alongside the first-observed entry to understand what each source captured. Keep the VirusTotal detection count and scanner total together as one record, and retain the PageSpeed score as its own separate measurement for future comparison.
Detection-evasion analysis
Cloaking suspected: scanner and visitor titles differ
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
IP ContextFastly shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerMarkMonitor(US)
HTTP Status404 Not Found
Time to First Unavailability4h
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
YR1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-13 01:15:45 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-10-09 01:25:25 UTCfirst terminal observation: 2026-10-01 01:39:05 UTC
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.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
Google PageSpeed Insights — mobile performance audit of sir-frotscher.github.io· checked Sep 11, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-11 10:00:14 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-11 05:26:37 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.199.111.153.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
sir-frotscher.github.io detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 11, 2026
Time to First Unavailability
4 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · sir-frotscher.github.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
