auforce.shop was observed returning an HTTP 200 status on 2026-10-08, indicating a successful web response at that time. The domain was also listed internally by PhishDestroy, which may warrant further attention from that source.
Recorded Evidence
OTX recorded three pulses for auforce.shop on 2026-10-08. VirusTotal reported 7 detections out of 92 scanners on the same date. The domain was registered with Dynadot Inc. on 2026-05-27, and its SSL certificate was issued by Let's Encrypt / YE1 as of 2026-10-08.
Interpretation
The evidence from OTX, VirusTotal, and PhishDestroy provides several perspectives on auforce.shop, with each source documenting its own observations. Technical details such as the HTTP response and SSL certificate add context to the domain's configuration, while detection counts and internal listings reflect external scrutiny. The dates allow for comparison of the domain's status across multiple platforms.
Recommended Actions
For auforce.shop, it is recommended to preserve the OTX, VirusTotal, and PhishDestroy records for ongoing reference. Review the HTTP response and SSL certificate details to monitor any changes in technical setup. Continued observation of these sources may help track future updates or shifts in the domain's recorded evidence.
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttp://auforce.shop/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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:16:51 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:16:51 UTClast content: 2026-10-11 10:16:51 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.
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
Bfore.Ai PreCrime
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of auforce.shop· checked Oct 8, 2026
55
Needs Work
Performance
FCP
3.04s
First Contentful Paint
LCP
12s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
280ms
Total Blocking Time
SI
11.18s
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-10-08 04:20:16 UTC
VirusTotal scanner detections updated from 0 to 7. Added scanner alerts: Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Netcraft, alphaMountain.ai.
Threat First Observed2026-10-07 22:14:22 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.229.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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)
