ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 7 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
skullchecker.com was checked by VirusTotal on 2026-09-29, recording 3 detections out of 92 scanners. The domain also received a PageSpeed performance score of 66 on 2026-10-06, indicating moderate responsiveness.
Recorded Evidence
VirusTotal observed skullchecker.com on 2026-09-29, noting 3 detections from 92 scanners. OTX pulses were recorded on 2026-10-07, with four entries. The domain was listed in the PhishDestroy internal catalogue as of 2026-10-07. Its SSL certificate was issued by Let's Encrypt / YR1 and scanned on 2026-10-07, while registration occurred on 2026-08-30 with Dominet (HK) Limited.
Interpretation
The evidence from VirusTotal and OTX provides insight into how skullchecker.com was evaluated by security sources in late 2026. The PageSpeed performance score and PhishDestroy listing offer additional context regarding site responsiveness and catalogue inclusion. Registration and SSL details reflect technical setup at the time of observation.
Recommended Actions
To maintain a clear record of skullchecker.com, preserve the VirusTotal detection history and OTX pulse entries for future comparison. Retain the PageSpeed score and PhishDestroy listing to monitor any changes in site responsiveness and catalogue status. These records should be referenced in subsequent reviews of the domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:08:42 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:33 UTClast content: 2026-10-13 22:08:42 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.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
Netcraft
SOCRadar
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of skullchecker.com· checked Oct 6, 2026
66
Needs Work
Performance
FCP
4.56s
First Contentful Paint
LCP
4.66s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
163ms
Total Blocking Time
SI
6.88s
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.
Threat First Observed2026-10-06 21:16:28 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.29.26.38.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
10 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)
