VirusTotal
15 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“C65”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 2 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
15 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 threat-system alerts
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | 65.jj38638.vip |
phishing | Phishing Block |
| DNS4EU | 65.jj38638.vip |
malicious | Sinkholed |
| Cloudflare DNS | 65.jj38638.vip |
malicious | Sinkholed |
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
Analysis indicates that the domain 65.jj38638.vip was registered on July 29, 2026 through Dynadot Inc. The authoritative name servers are n1.xundns.com and n2.xundns.com, and DNS resolution points to the IPv4 address 40.81.25.117. The domain currently appears on a single security blocklist and is listed as blocked by PhishDestroy, confirming active use in malicious campaigns. VirusTotal data show that six of ninety‑one scanning engines have flagged the domain, providing independent corroboration of its malicious reputation. The presence on PhishDestroy indicates that the domain has been observed delivering credential‑harvesting pages, although the specific landing page has not been publicly disclosed.
No additional public intelligence such as Safe Browsing verdicts, OTX references, SSL certificate details, HTTP response codes, or page‑title information is presently available, limiting the ability to characterize the exact phishing payload or targeted brand. The IP address 40.81.25.117 is hosted in a cloud environment that historically has been abused for short‑term phishing hosting, but no ASN or country attribution is provided in the current feed. The limited detection footprint combined with recent registration suggests a short‑lived infrastructure typical of opportunistic phishing operators. Defenders should add 65.jj38638.vip to URL filtering and DNS sinkhole rules, monitor outbound connections to 40.81.25.117, and enforce blocklist updates that include this domain.
Because the registrar is Dynadot Inc, threat‑intel teams may consider requesting WHOIS amendment logs or abuse contacts for possible takedown. Organizations should prioritize detection of outbound traffic to this address and consider employing heuristic or machine‑learning models that flag newly created domains with similar characteristics. Integration of this indicator into SIEM correlation rules can help surface related phishing attempts that may use the same infrastructure.
22 · datasets with records / 9 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Dynadot Inc · 40.81.25.117 · DNS, TLS and retained responses
For the registrable domain jj38638.vip behind this subdomain, 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.
n1.xundns.comn2.xundns.comLocation describes the IP network.
ca703b31bcbd692ab9f2366ae9cffd732ba399d1dd581a14038b646f53b34efa65.jj37664.vip65.jj38207.vip65.jj38212.vip65.jj38215.vip65.jj38228.vip65.jj38232.vip65.jj38233.vip65.jj38234.vip65.jj38243.vip65.jj38244.vip65.jj38245.vip65.jj38265.vip65.jj38269.vip65.jj38277.vip65.jj38288.vip65.jj38292.vip65.jj38297.vip65.jj38302.vip65.jj38304.vip65.jj38305.vip65.jj38307.vip65.jj38310.vip65.jj38313.vip65.jj38322.vip65.jj38323.vip65.jj38327.vip65.jj38331.vip65.jj38337.vip65.jj38340.vip65.jj38357.vip65.jj38358.vip65.jj38360.vip65.jj38363.vip65.jj38366.vip65.jj38370.vip65.jj38371.vip65.jj38374.vip65.jj38380.vip65.jj38384.vip65.jj38385.vip65.jj38393.vip65.jj38394.vip65.jj38396.vip65.jj38397.vip65.jj38398.vip65.jj38403.vip65.jj38406.vip65.jj38407.vip65.jj38408.vip65.jj38409.vip65.jj38412.vip65.jj38420.vip65.jj38421.vip65.jj38423.vip65.jj38424.vip65.jj38428.vip65.jj38431.vip65.jj38443.vip65.jj38444.vip65.jj38457.vip65.jj38460.vip65.jj38461.vip65.jj38462.vip65.jj38469.vip65.jj38472.vip65.jj38475.vip65.jj38476.vip65.jj38478.vip65.jj38479.vip65.jj38481.vip65.jj38484.vip65.jj38499.vip65.jj38524.vip65.jj38546.vip65.jj38560.vip65.jj38562.vip65.jj38581.vip65.jj38587.vip65.jj38648.vip65.jj38655.vip65.jj38666.vip65.jj38668.vip65.jj38670.vip65.jj38683.vip65.jj38684.vip65.jj38686.vip65.jj38689.vip65.jj38693.vipSaved 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 65.jj38638.vip · checked Aug 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
No live-check result has been retained.
1 · outbound report records
40.81.25.117.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
Reachable
10 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260806-F1C66B Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Recovery steps, reporting contacts and complaint drafts
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
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 ↗
65.jj38638.vip)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “C65”.
VirusTotal detections for 65.jj38638.vip: 15 (2026-09-13 02:10:10 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.