On 2026-10-05 the domain aspgear.shop returned a recorded response, and HMZ Web Hosting Co hosts the associated IP address 195.96.130.242. The domain spelling alone does not indicate the type of content or services offered.
Recorded Evidence
aspgear.shop was first observed on 2026-10-05, and the IP address 195.96.130.242 is located in the US under HMZ Web Hosting Co. OTX recorded 4 pulses on 2026-10-05, and the SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-10-05. The publisher-owned PhishDestroy catalogue listed aspgear.shop on 2026-10-05.
Interpretation
The dated records span hosting location, threat intelligence, and publisher listing without implying causation or activity. The SSL scan and OTX pulses were recorded on the same date as the first observation, so no sequence can be inferred. The presence of a listing in the PhishDestroy catalogue indicates a publisher flag but does not establish ongoing content or intent.
Recommended Actions
Review the domain aspgear.shop against the PhishDestroy catalogue entry and compare it with OTX pulses for context. Verify the SSL certificate details and hosting provider information for consistency with expected configurations. Maintain updated records of these sources to support ongoing monitoring decisions.
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:38:56 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:38:56 UTClast content: 2026-10-11 10:38:56 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: 5 detections
alphaMountain.ai
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
ネットクラフト
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of aspgear.shop· checked Oct 5, 2026
74
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
5.33s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
123ms
Total Blocking Time
SI
3.41s
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-05 06:08:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.242.
脅威対応 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.
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)
