Security engines reporting a detection: 19. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@microsoft.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.
Analysis indicates that the domain 65.jj38390.vip is presently active and associated with a phishing campaign. The domain resolves to the IPv4 address 104.208.98.216, confirming that traffic is directed to a single host. Infrastructure monitoring shows that the domain has been added to at least one external security blocklist and was explicitly blocked by the PhishDestroy filtering service, reinforcing the assessment of malicious intent. VirusTotal scanning recorded detections from six out of ninety‑one antivirus and URL‑reputation engines, providing independent confirmation that the domain exhibits characteristics commonly observed in phishing infrastructure.
Nameserver information could not be retrieved, which may reflect the use of dynamic or obscured DNS configurations intended to hinder attribution. No SSL certificate details, HTTP status codes, or page title information are available in the current intelligence set, and the registrar metadata is absent, limiting the ability to trace ownership or hosting provider. The limited visibility into the web content means the exact phishing lure or target brand cannot be identified at this stage.
Given the confirmed detections, blocklist presence, and active status, defenders should treat the domain as high‑risk: network firewalls and DNS resolvers ought to deny queries to 65.jj38390.vip, the associated IP 104.208.98.216 should be added to deny lists, and security appliances should continue to monitor for any outbound connections to that address. Continuous re‑evaluation is advised, including periodic rescans, sandbox execution of any retrieved payloads, and correlation with threat‑intel feeds to capture potential evolution of the campaign. Until further evidence emerges, the precautionary stance remains to block and monitor all activity linked to this domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Certificate hostname mismatch·
Issued by Let's Encrypt· stored validity ends in 87 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
104.208.98.216
Network ASN
AS8075
Organization
Microsoft Azure Cloud (eastasia)
Observed location
Hong Kong, HK
Server header
nginx
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-07-28 06:46:56
Valid until
2026-10-26 06:46:55
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-07-30 13:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbbb88fee7aeedf8407e7a77b1c7eea6f1e70d553abfc0091c668723cd58a20d0Certificate names · 4 SANs
65.jj38219.vip
65.jj38268.vip
65.jj38315.vip
65.jj38349.vip
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: StaleRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-08 10:26:44 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-08 10:26:44 UTClast content: 2026-10-08 10:26:44 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Values retained by the collector; long values may be shortened during collection.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-07-30 12:21:17 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.208.98.216.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
65.jj38390.vip detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · 65.jj38390.vip
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
Report 
