VirusTotal
2 / 91 engine detections
Buka laporan“The Eternal — Your Wisdom, Forever”
Security analysis of www.theeternal.love covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
2 / 91 engine detections
Buka laporanno community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
henry.ns.cloudflare.comkhloe.ns.cloudflare.comLocation describes the IP network.
79f328d86d67032761c3c422ca9cc33386bfec78f7f912be63c6fa4a9b26a031Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-377224.invalid · checked Aug 4, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
2/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceduplicate-disabled-377224.invalid
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
duplicate-disabled-377224.invalid
Listed domains receive at least one abuse report; this entry has no retained notification history.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
duplicate-disabled-377224.invalid)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.