VirusTotal
5 / 89
Security analysis of turtle.claims covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
Analysis of turtle.claims, registered through NICENIC INTERNATIONAL GROUP CO., LIMITED on July 31, 2026, indicates active malicious infrastructure targeting cryptocurrency assets. The domain resolves to the IP address 172.67.158.71 and is served via Cloudflare, as evidenced by the authoritative nameservers chuck.ns.cloudflare.com and rafe.ns.cloudflare.com. The hosting choice suggests the operators are leveraging Cloudflare's CDN and obfuscation capabilities to hide the true origin of the payload. Turtle.claims appears on three independent security blocklists and has been explicitly blocked by PhishDestroy, MetaMask, and SEAL, reinforcing the assessment that the site is being used to lure victims into unauthorized crypto transactions.
VirusTotal scans show three of ninety‑one security vendors flagging the domain, providing additional vendor‑level corroboration of malicious intent. The threat classification is identified as a "crypto drainer," implying that the site likely attempts to intercept or redirect cryptocurrency withdrawals, though specific tactics (e.g., malicious smart‑contract injection, phishing of wallet credentials) have not been publicly disclosed. Open Threat Exchange (OTX) references or Safe Browsing verdicts are not currently available, and no page title or content analysis has been published, leaving the exact user‑facing experience unverified.
Defenders should proactively block network traffic to 172.67.158.71, enforce domain‑level denial for turtle.claims across proxy and firewall rules, and monitor for any DNS queries to the associated Cloudflare nameservers. Endpoint security solutions should be updated to recognize the three vendor detections reported by VirusTotal, and organizations using cryptocurrency wallets should educate users about the risk of unsolicited wallet‑address requests. Continuous re‑evaluation is recommended as additional intelligence, such as page content snapshots or OTX indicators, become available.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
chuck.ns.cloudflare.comrafe.ns.cloudflare.comLocation describes the IP network.
1b60f482a32ad74285aab98344d0929ae645bf88680425abf849cc772e8a539dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
172.67.158.71. 26 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
79 stored lookalike domains
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive