Analysis of www.pdfearth.com (created 2026-07-04) shows that the domain is registered through Spaceship, Inc. with authoritative nameservers launch1.spaceship.net and launch2.spaceship.net. DNS resolution points to the IPv4 address 64.29.17.65, which remains active at the time of the report (2026-08-04). The domain has been observed on a single security blocklist and is actively blocked by the PhishDestroy service. A VirusTotal scan performed on the domain was submitted to 91 antivirus and URL‑reputation vendors; none of the vendors reported a detection at the time of scanning.
No additional public reputation sources such as Google Safe Browsing, OTX, or SSL/TLS certificate transparency logs have been disclosed for this host. The page title, HTTP response code, and any TLS certificate details have not been published, leaving the exact nature of the hosted content unknown. The available evidence therefore confirms the presence of a newly registered domain that is being used for a generic phishing campaign, but the lack of content‑level analysis prevents a precise attribution of the phishing kit or targeted brand.
Defenders should treat the domain as malicious, enforce network‑level blocks to the IP address 64.29.17.65, add www.pdfearth.com to URL filtering policies, and monitor the associated nameservers for future sub‑domain creations. Continuous re‑scanning with VirusTotal and inclusion in threat‑intel feeds are recommended to capture any changes in detection status. Organizations that employ email gateway or web‑proxy solutions should ensure that traffic to this domain is denied, and incident response teams should be prepared to investigate any credential‑theft attempts that reference pdfearth.com.
DOM Analysisanalyzed 2026年8月4日score 71/1001 brand signal
Submitted URLhttps://www.pdfearth.com/
Favicon Hash
ケース ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
