Analysis of www.theeternal.love shows that the domain was registered on July 06, 2026 through Cloudflare, Inc. The authoritative nameservers are henry.ns.cloudflare.com and khloe.ns.cloudflare.com, both belonging to Cloudflare’s DNS infrastructure. DNS resolution returns a single IPv4 address, 216.150.1.193, which is the only host observed for this domain. The IP address is not currently associated with any known benign services and is listed on one public security blocklist. The blocklist entry is also reflected in the PhishDestroy feed, which has actively blocked the domain.
VirusTotal has processed the domain with 91 scanning engines; none of the engines raised a detection at the time of analysis, but the absence of detections does not constitute a safety assurance. No public Safe Browsing, Open Threat Exchange, SSL certificate, HTTP response code, or trust‑score data were found for the domain, and the page title has not been disclosed. Consequently, the observable infrastructure points to a newly created site that is already being used for generic phishing, as indicated by the threat classification provided.
Defenders should add the domain and its IP address to blocklists, monitor DNS queries for the two Cloudflare nameservers, and enforce outbound filtering to prevent credential submission to the host. Continuous re‑scanning with VirusTotal and other multi‑engine services is recommended, as additional detections may appear if the site begins to host malicious payloads. Network‑level controls that restrict traffic to the identified IP and that enforce TLS inspection where possible will reduce exposure while further investigation is underway.
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)
