autofinessecare.shop was first observed on 2026-10-08, with VirusTotal reporting 0 detections from 92 scanners on that date. The domain received a PageSpeed performance score of 67, indicating moderate technical responsiveness.
Recorded Evidence
VirusTotal checked autofinessecare.shop on 2026-10-08, recording zero detections from 92 scanners. OTX pulses were noted at 4 as of 2026-10-08. The domain appeared in the PhishDestroy internal listing on 2026-10-08. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-08.
Interpretation
These dated source observations provide a technical overview of autofinessecare.shop, allowing comparison of cataloguing and performance across monitoring services. The VirusTotal, OTX, and PhishDestroy records highlight the domain's presence in multiple catalogues, while the PageSpeed score and SSL certificate details offer insight into its technical setup.
Recommended Actions
For autofinessecare.shop, it is advisable to preserve the VirusTotal and OTX records for ongoing review. Retaining the PhishDestroy internal listing and PageSpeed performance score will support future comparisons. Source records should be archived to track any changes or new observations.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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-11 10:00:50 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:00:50 UTClast content: 2026-10-11 10:00:50 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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of autofinessecare.shop· checked Oct 8, 2026
67
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
5.56s
Largest Contentful Paint
CLS
0.019
Cumulative Layout Shift
TBT
298ms
Total Blocking Time
SI
4.06s
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-08 12:00:46 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 195.96.130.228.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月8日
Brand Impersonation
Impersonation of Fakeshop
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
