The domain apbrew.shop was recorded with 8 detections out of 91 scanners in a VirusTotal check dated 2026-10-01. Separately, the PhishDestroy internal catalogue listed apbrew.shop, and OTX recorded one pulse for the domain on 2026-10-02.
Recorded Evidence
VirusTotal reported 8 detections from 91 scanners for apbrew.shop on 2026-10-01. OTX recorded one pulse for apbrew.shop as of 2026-10-02. The PhishDestroy internal listing for apbrew.shop was recorded on 2026-10-02. A PageSpeed check on 2026-10-02 returned a performance score of 82 for apbrew.shop. The domain resolved to IP address 195.96.130.231, associated with HMZ Web Hosting Co in the US.
Interpretation
The VirusTotal figures describe scanner output for apbrew.shop on a single date, while the OTX pulse count reflects a separate source's record. The PhishDestroy catalogue entry and the PageSpeed score come from different checks, so their values should be read individually rather than combined. The 2026-10-01 and 2026-10-02 dates show the records were collected on adjacent days, not that any condition changed.
Recommended Actions
For apbrew.shop, preserve the VirusTotal detection record and the OTX pulse entry for later comparison. Keep the PhishDestroy catalogue listing and the PageSpeed performance score as separate reference points. Compare each source record against future checks of apbrew.shop to see whether the recorded values shift.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='apbrew.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:08:40 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-03 10:12:24 UTCcurrent episode first observed: 2026-10-05 22:13:39 UTCobserved RIP window: 2026-10-03 10:12:24 UTC → 2026-10-05 22:13:39 UTC · 60.02hmidpoint estimate ≈ 2026-10-04 16:13:01 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.
使用技術 · 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 apbrew.shop· checked Oct 2, 2026
82
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
3.53s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
214ms
Total Blocking Time
SI
2.86s
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-02 18:18:15 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.231.
脅威対応 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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)
