The domain patrickcoin.online was registered on October 17 2025 via Hostinger operations, UAB. It resolves to the IP address 188.114.96.3, which belongs to AS13335 Cloudflare, Inc., located in the United States. The site was observed to serve a page titled "Patrick Coin Airdrop" and is identified as a wallet/seed phishing operation that impersonates Discord. The infrastructure uses Cloudflare nameservers louis.ns.cloudflare.com and veronica.ns.cloudflare.com, but no TLS certificate was presented, indicating that the site was reachable only over HTTP.
The domain has been taken offline, and its status is currently listed as offline. It appears on two security blocklists and is explicitly blocked by PhishDestroy and ScamSniffer. VirusTotal analysis shows that two of ninety‑five security vendors flagged the domain as malicious. The phishing kit in use is labeled as an "Airdrop Scam" kit, which is commonly employed to lure victims into submitting cryptocurrency wallet seeds.
While the site is no longer active, the hosting IP remains under Cloudflare control and could be reused for future campaigns. Defenders should continue to block the domain and its associated IP at perimeter defenses, add the domain to internal phishing blocklists, and monitor for any re‑registration attempts. Users should be warned that any unsolicited Discord‑related airdrop requests from this domain are fraudulent, and they should never share private keys or seed phrases. Ongoing observation of the Cloudflare IP range for similar activity is recommended.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='patrickcoin.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
DOM Analysisanalyzed 2026年3月24日score 25/1003 brand signals
Submitted URLhttp://patrickcoin.online/
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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:10:42 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-10 04:44:18 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-10 04:44:18 UTC → 2026-09-30 16:14:55 UTC · 4,163.51hmidpoint estimate ≈ 2026-07-05 22:29:36 UTC · precision very 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.
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.
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.
(LT)
