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.
poolmrkt.top returned an HTTP 301 status code on 2026-10-01, a dated response recorded during an HTTP check. The domain was first observed on 2026-09-17, according to the same evidence set.
Recorded Evidence
An HTTP check on 2026-10-01 recorded status 301 for poolmrkt.top. VirusTotal reported 6 detections across 91 scanners on 2026-09-27. OTX listed 3 pulses as of 2026-09-23. The PhishDestroy internal listing includes this domain. The registrar is NICENIC INTERNATIONAL GROUP CO., LIMITED, with registration dated 2026-09-09. The SSL certificate, issued by Let's Encrypt / YE2, was scanned on 2026-09-21.
Interpretation
The VirusTotal detection count and scanner total describe only what that platform recorded on its check date. The OTX pulse count reflects how many OTX pulses referenced the domain at its check time. The PhishDestroy internal listing records catalogue inclusion without describing content. These dated records allow comparison across sources, but each covers a different scope and measurement.
Recommended Actions
For poolmrkt.top, retain the VirusTotal, OTX, and PhishDestroy records, and preserve the HTTP response record for later comparison. Compare future VirusTotal and OTX observations against these saved records to identify changes. Recheck the HTTP status and record the result alongside the existing response entry.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 11:00:10 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 11:00:10 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.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
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.
Threat First Observed2026-09-21 10:23:09 UTC
Domain ingestion complete. Initial state is marked as alive.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
脅威の検知
poolmrkt.top 検出され、詳細な分析のためにキューに入れられた
2026年9月17日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年9月21日
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.
(RU)
PhishDestroy Investigation
