On 2026-10-01, accounts-google-login.github.io returned HTTP status 404 according to the recorded HTTP check. A separate Google Safe Browsing check on 2026-09-15 flagged the domain for social engineering, and the PhishDestroy internal listing also records it.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 404 for accounts-google-login.github.io. Google Safe Browsing, checked on 2026-09-15, flagged the domain with the threat label social engineering. VirusTotal, also checked on 2026-09-15, reported 16 detections across 89 scanners. The PhishDestroy internal listing records the domain, and first observation is dated 2026-09-08. The SSL scan on 2026-09-08 identified the issuer as Let's Encrypt / YR1, and the PageSpeed check that same date recorded a performance score of 100.
Interpretation
The dated records describe different measurement types rather than a single consistent signal. The Safe Browsing flag and the VirusTotal detection count come from separate sources checked on the same calendar date, but that shared date does not establish simultaneous measurement or direct comparability. The HTTP 404 describes only the response recorded on its own check date and does not establish present availability. The first observation and SSL scan dates show when records began, not a sequence of events.
Recommended Actions
Preserve the recorded HTTP response, the Safe Browsing flag, the VirusTotal detection count and the PhishDestroy listing for accounts-google-login.github.io as separate source records. Compare the HTTP response and the Safe Browsing flag in separate reviews rather than merging them into one judgment. Retain the VirusTotal detection count alongside its total scanner figure for later comparison. Keep the PhishDestroy listing and the first observation record available for reference.
Detection-evasion analysis
Cloaking and traffic-distribution check
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.
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.
Technical detailsProvenance & timestamps
First DetectedSep 8, 2026
DOM Analysisanalyzed Sep 8, 2026score 100/1001 brand signal
Certificate hostname mismatch·
Issued by Let's Encrypt· stored validity ends in 53 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.108.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
GitHub.com
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-08 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84Certificate names · 3 SANs
github.com
github.io
githubusercontent.com
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-11 01:14:23 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-08 09:56:49 UTCcurrent episode first observed: 2026-10-09 01:25:15 UTCobserved RIP window: 2026-09-08 09:56:49 UTC → 2026-10-01 01:38:51 UTC · 543.70hmidpoint estimate ≈ 2026-09-19 17:47:50 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.
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.
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
URLQuery
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of accounts-google-login.github.io· checked Sep 8, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
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.
VirusTotal Detections Update2026-09-15 17:05:55 UTC
VirusTotal scanner detections updated from 15 to 16. Added scanner alerts: MalwareURL.
VirusTotal Detections Update2026-09-14 06:27:01 UTC
VirusTotal scanner detections updated from 11 to 15. Added scanner alerts: BitDefender, Forcepoint ThreatSeeker, Lionic, URLQuery.
Domain Status Transition2026-09-10 22:04:38 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-08 10:00:06 UTC
Telemetry event observed.
Threat First Observed2026-09-08 09:56:49 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.199.108.153.
Threat Response Pipeline
Discovery
Analysis
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
accounts-google-login.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
60 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 →
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.
Content matches8
Same favicon hash or the same page title as this host.
