naturiumaf.shop returned HTTP status 502 in the response recorded on 2026-10-01, a dated observation of the domain's HTTP behavior. The domain was first observed on 2026-09-02, according to the available record.
Recorded Evidence
Google Safe Browsing flagged the domain on 2026-09-13 with a social engineering threat. VirusTotal recorded 5 detections across 89 scanners on 2026-09-13. OTX showed 4 pulses on 2026-09-13. The domain appears in the PhishDestroy internal listing, and the registrar is Spaceship, Inc.
Interpretation
The HTTP 502 response describes only what was returned on the recorded date and does not establish the domain's current availability or its content. The Safe Browsing flag, VirusTotal detections, and OTX pulses are separate source observations, each tied to its own check date, and they should be compared as distinct records rather than merged into a single verdict. The chronology from first observation to the later checks is useful for ordering when each record was captured, not for proving a trend.
Recommended Actions
Preserve the HTTP response record for naturiumaf.shop and the PhishDestroy internal listing as separate source records. Compare the Safe Browsing flag against the VirusTotal and OTX observations in separate sentences when reviewing the domain. Treat each dated source record as its own data point when deciding on next steps for naturiumaf.shop.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='naturiumaf.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:15:59 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-02 05:28:14 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-02 05:28:14 UTC → 2026-09-30 16:14:55 UTC · 682.78hmidpoint estimate ≈ 2026-09-16 10:51:34 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Gridinsoft
Lionic
PhishFort
SOCRadar
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.
Domain Status Transition2026-09-13 10:00:19 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-13 08:30:04 UTC
Telemetry event observed.
Threat First Observed2026-09-13 08:23:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
naturiumaf.shop 已检测到并排入队，待进行全面分析
2026年9月2日
Cloudflare Radar Report
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)
