The domain spotfjfhh-crypto.github.io returned an HTTP 404 status on 2026-10-01, indicating no content was available at that time. It was also noted for a high performance score in a PageSpeed check on 2026-09-07.
Recorded Evidence
An HTTP check on 2026-10-01 recorded a 404 response for spotfjfhh-crypto.github.io. VirusTotal scanned the domain on 2026-09-11, reporting 14 detections out of 89 scanners. The domain was listed in the PhishDestroy internal catalogue. The SSL certificate was issued by Let's Encrypt / YR1 and scanned on 2026-09-07.
Interpretation
These records show that spotfjfhh-crypto.github.io was reviewed by multiple sources over several dates. The HTTP 404 status documents a lack of accessible content at the time of that check, while the VirusTotal and PhishDestroy entries indicate it was subject to security-related scrutiny. The SSL certificate details and performance score provide additional context for technical assessment.
Recommended Actions
Preserve the HTTP response, VirusTotal scan, and PhishDestroy listing records for spotfjfhh-crypto.github.io for future reference. Compare these dated observations with subsequent findings to track any changes in the domain's status or security profile.
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 7, 2026
DOM Analysisanalyzed Sep 7, 2026score 78/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.109.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-07 13: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:19 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-07 12:20:02 UTCcurrent episode first observed: 2026-10-09 01:25:04 UTCobserved RIP window: 2026-09-07 12:20:02 UTC → 2026-10-01 01:38:37 UTC · 565.31hmidpoint estimate ≈ 2026-09-19 06:59:19 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: 11 detections
Criminal IP
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
LevelBlue
Netcraft
Sophos
URLQuery
VIPRE
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of spotfjfhh-crypto.github.io· checked Sep 7, 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.
VirusTotal Detections Update2026-09-10 22:31:50 UTC
VirusTotal scanner detections updated from 11 to 14. Added scanner alerts: BitDefender, Criminal IP, VIPRE.
Domain Status Transition2026-09-10 22:04:18 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-08 11:45:55 UTC
VirusTotal Detections Update2026-09-08 10:13:28 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-09-07 12:20:02 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.199.109.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
spotfjfhh-crypto.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
81 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 · spotfjfhh-crypto.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.
Content matches8
Same favicon hash or the same page title as this host.
