Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain herti9hye.beer returned HTTP status 502 on 2026-10-01, a server-side error recorded at that check. Separately, the domain was first observed on 2026-09-13, and its registration date is listed as 2026-08-27 with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED.
Recorded Evidence
VirusTotal recorded 4 detections across 89 scanners on 2026-09-21. OTX recorded 6 pulses on 2026-09-21. The domain appears on two external blocklists, MetaMask and SEAL, as of the 2026-10-01 blocklist check. PhishDestroy holds an internal listing for herti9hye.beer, and the HTTP check on 2026-10-01 returned status 502.
Interpretation
The named sources describe different scopes: an HTTP response code reflects one request at one time, while blocklist and pulse entries reflect separate collection processes. Because the VirusTotal and OTX observations share a calendar date, they do not establish simultaneous measurement or direct comparability. The gap between the first observation and the later checks is a matter of record only, not evidence of a trend.
Recommended Actions
Preserve the VirusTotal and OTX records for herti9hye.beer so future checks can be compared against them. Retain the MetaMask and SEAL blocklist entries alongside the PhishDestroy internal listing for the same domain. Compare later HTTP responses for herti9hye.beer with the recorded status to see whether the response pattern changes.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='herti9hye.beer', 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-12 10:55:50 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-13 05:28:07 UTCcurrent episode first observed: 2026-09-19 06:02:46 UTCobserved RIP window: 2026-09-13 05:28:07 UTC → 2026-09-19 06:02:46 UTC · 144.58hmidpoint estimate ≈ 2026-09-16 05:45:26 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: 4 detections
alphaMountain.ai
CRDF
Fortinet
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.
VirusTotal Detections Update2026-09-20 18:47:21 UTC
VirusTotal scanner detections updated from 2 to 4. Added scanner alerts: CRDF, SOCRadar.
Domain Status Transition2026-09-19 22:00:24 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-19 18:21:07 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 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.
We are writing to report a registered domain name that is being used to publish cryptocurrency phishing pages under the names of two crypto products.
The name itself is a random string with nothing behind it. A request to herti9hye[.]beer is answered with a bare "403 Forbidden"
1 report filed for herti9hye.beer (1 written by a person) · category: Phishing · source checked
“We are writing to report a registered domain name that is being used to publish cryptocurrency phishing pages under the names of two crypto products.
The name itself is a random string with nothing behind it. A request to herti9hye[.]beer is answered with a bare "403 Forbidden" page from nginx, and the same answer comes back from meteora[.]herti9hye[.]beer when the address is typed in directly. The fraud is carried on hosts published beneath the registration — meteora[.]herti9hye[.]beer and rab”
— reported by Anonymous on Sep 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
(RU)
PhishDestroy Investigation
