VirusTotal
18 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Domain security report
j62q.vip
“welcome-BET365”
Threat verdict
CriticalDomain Appeal
Assessment sources
Assessment based on the stored source evidence below. Review sources →
Availability
Last known active
Latest stored reachability observation
Observed · HTTP probe
Risk signals
VirusTotal detections: 18/91
Spamhaus DBL: DBL_SPAM
URLQuery threat systems: 9 alerts
Automated brand label: Bet365
- Registrar
- NameMart
- Resolved IP
- 154.39.104.138
- Registered
- May 17, 2026
Stored captures
3 sourcesThe capture source is temporarily unavailable.
In this reportGet help
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@namemart.com.
The latest stored availability evidence still shows the domain reachable; 3 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.
Elapsed since first report
3 months
Reports sent
1
Latest case ID
PD-20260717-FCFB10
Current status
HTTP 200 at latest stored check
Additional indicators at a glance
Spamhaus DBL
DBL_SPAM
VirusTotal
18 det.
URLQuery
9 threat alerts
OTX references
CF Radar
Malicious
URLScan
Scamadviser
80/100Likely Safe
TLS Certificate
Hostname mismatch -36d
Let's Encrypt / YR1 · Certificate hostname mismatchAge
5 mo
Observed status
Last known active 200
DestroyList
Listed
Reports Sent
1
Source evidence
10 · sourcesThese 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.
URLQuery
9 threat-system alerts
ReportInterpretation & limits
Alerts refer to the preserved scan. They do not describe the current state of the site.
CF Radar
provider verdict: malicious
Observation time not recorded
Report Interpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Spamhaus DBL
DBL_SPAM
Interpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
OTX
5 community references
ReportInterpretation & limits
Community publication references, not a vendor verdict or evidence of a common operator.
URLScan capture
stored report
View stored capture ↗ ReportInterpretation & limits
A preserved page image documents what the collector received; a capture is not a safety verdict.
URLScan verdict
Analysis completed
ReportInterpretation & limits
This is the recorded automated analysis. Completion alone is not a safety verdict.
Scamadviser
80/100
Observation time not recorded
Report Interpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Google Safe Browsing
Checked; no threat flag recorded
ReportInterpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Public blocklists
0 external matches
DetailsInterpretation & limits
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Network Security Intelligence
Threat Detection Systems
9 alerts
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | 17651.xyz |
malicious | Sinkholed |
| DNS4EU | img.esportsdata.cc |
malicious | Sinkholed |
| Hagezi Threat Feed | img.esportsdata.cc |
malicious | Sinkholed |
| DNS4EU | ssl.hw301.xyz |
malicious | Sinkholed |
| Cloudflare DNS | j62q.vip |
malicious | Sinkholed |
| OpenDNS | j62q.vip |
phishing | Phishing Block |
| Hagezi Threat Feed | j62q.vip |
malicious | Sinkholed |
| DigiCert UltraDNS | j62q.vip |
malicious | Sinkholed |
| DNS4EU | j62q.vip |
malicious | Sinkholed |
Evidence Summary
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.
The domain j62q.vip was registered on May 17, 2026 through NameMart Pte. Ltd. and remains active as of the report date. It resolves to the IPv4 address 103.27.177.164 and is hosted on a set of four name servers (ns1-4.1111343.com), suggesting a potentially shared or disposable hosting environment. VirusTotal analysis shows that 7 of 91 security vendors have flagged the domain, indicating that multiple detection engines have identified malicious characteristics associated with the host. The threat classification is generic_phishing and the risk level is high, implying that the domain is likely being used to harvest credentials or personal data. Concrete evidence beyond the infrastructure details and the VirusTotal detections is not presently available; no page content, brand targeting, or specific phishing lure has been disclosed. Because the domain’s infrastructure is simple and the hosting appears to be generic, it is plausible that the operator can rapidly replace the site if taken down. Defenders should prioritize immediate blocking of j62q.vip at the DNS and proxy layers, enforce outbound filtering to the IP 103.27.177.164, and monitor the associated name servers for any sudden changes. Continuous re‑scanning of the domain on multi‑engine platforms is advised to capture any evolution in malicious behavior. Organizations should also educate users about unsolicited credential‑request emails that may reference this domain, even though the exact phishing content has not been publicly observed.
Data coverage & collection
19 · datasets with records / 12 · 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.
Recorded dataPartial recordUTC
- VirusTotal
- 18 / 91 · engine detections
- URLScan analysis
- Automated verdict retained
- URLQuery
- 9 · recorded detections / alerts
- Google Safe Browsing
- Checked; no threat flag recorded
- OTX publications
- 5 · community references
- External blocklists
- 0 · external matches
- Cloudflare Radar
- maliciousCollection time not recorded
- Scamadviser
- 80/100 · provider trust scoreCollection time not recorded
- Spamhaus DBL
- DBL_SPAM
- Domain registration
- NameMart Pte. Ltd.Collection time not recorded
- Network & DNS
- 154.39.104.138 · 4 · nameserversCollection time not recorded
- TLS certificate
- Let's Encrypt / YR1
- Page captures
- 3 · retained captures
- Page analysis
- 1 · automated brand labels
- Observed indicators
- 0 · wallet / Telegram indicators
- Detection & evasion
- Stored browser and crawler comparison
- Response records
- 1 · outgoing report records
- Availability history
- 30 · stored state changes
- IP reputation
- Network-level observations
Not recorded in this report 12
These checks have no retained result. This does not mean they passed or that a scan is running.
- PhishStats
- DNS security filters
- Gridinsoft
- HTML archives
- Site configuration files
- PageSpeed performance
- Recorded subdomains
- Source observation history
- Lookalike relationships
- Community reports
- Chainabuse records
- Wayback archive
Download the dated observations and supporting metadata.
Blocklist records
0 · external source matches
Public Blocklist Status
Domain, network & archive
NameMart Pte. Ltd. · 154.39.104.138 · DNS, TLS and retained responses
Domain details
Domain
URLScan verdict
Analysis completed
score 0 report ↗
IP Reputation
abuse score 0/100 0 reports checked Oct 14, 2026
OTX tags
Registrar
NameMart
(CN)
(CN)
RegistrationCreated May 17, 2026 (153d) — Expires May 17, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJul 16, 2026
DOM Analysis
Submitted URLhttp://j62q.vip/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
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.
Accreditation is a contract, not a safety seal.
Verify ICANN fees
Read RAA §3.18
PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Network & certificates
Stored technical evidenceNetwork & DNS
- Resolved IP
- 154.39.104.138
- Network ASN
- AS18186
- Organization
- AS135357 HONG KONG KOWLOON TELECOMMUNICATIONS CO.,LIMITED
- Observed location
- Hong Kong, HK
- Server header
- Nginx
Nameservers 4
ns1.1111343.comns2.1111343.comns3.1111343.comns4.1111343.com
Location describes the IP network.
TLS certificate
- Issuer
- Let's Encrypt / YR1
- Valid from
- 2026-06-14 14:57:30
- Valid until
- 2026-09-12 14:57:29
- Hostname coverage
- Certificate hostname mismatch
- Validity
- Stored certificate expired
- Collection time
- 2026-07-16 13:00:07 UTC
- Collection source
- PhishDestroy collector
Certificate fingerprint
be4eb821b8163704242c9f0a483bc6129bd282f50e4cb5677fc6898069e5476eCertificate names · 48 SANs
j59l.vipj59m.vipj59n.vipj59o.vipj59t.vipj59u.vipj59v.vipj59w.vipj59x.vipj59y.vipj59z.vipj60a.vipj62p.vipj62r.vipj62s.vipj62t.vipj62u.vipj62v.vipj62w.vipj63h.vipj63i.vipj63j.vipj63k.vipj63l.vipj63m.vipj65u.vipj65v.vipj65w.vipj65x.vipwww.j59k.vipwww.j59l.vipwww.j59m.vipwww.j59t.vipwww.j59u.vipwww.j59v.vipwww.j59w.vipwww.j59x.vipwww.j59y.vipwww.j59z.vipwww.j60a.vipwww.j65u.vipwww.j65v.vipwww.j65w.vipwww.j65x.vipwww.j67d.vipwww.j67e.vipwww.j67f.vipwww.j67g.vip
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest Classified Outcome 2026-10-17 10:19:04 UTC
Primary outcome
Live content
reason: Ordinary HTTP content served 90% confidence
Attribution
source: Current Http Probe
Evidence layers
Availability: Content serving
Content: Content served at root
DNS: Resolved
Registration: Unknown
Latest HTTP observation
Live content Ordinary HTTP content served 90% 2026-10-17 10:19:04 UTC
RDAP registration
Unknown
Observed timeline
last reachable: 2026-10-17 10:19:04 UTC last content: 2026-10-17 10:19:04 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 · 5 identified
Vue.js
JavaScript frameworks
Nginx
Web servers
Reverse proxies
HSTS
Security
Cloudflare
CDN
HTTP/3
Miscellaneous
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain
Submit evidence & help protect others
VirusTotal Analysis
18 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 19 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Registration & observation details3
Availability observations
- Last reachable observation
- Last content observation
- Estimate basis
- Currently reachable
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Detection & evasion checks
Stored browser and crawler observations
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scanned
No 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.
- Stored cloaking flag
- Not yet scanned
- Last cloaking scan
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered
Timeline & response
1 · outbound report records
Stored observation history30
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
Earlier observations 25
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
live_content→Unknown
stale_current_evidence
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
live_content→Unknown
probe_inconclusive
-
Availability monitor · Recorded state
Unknown→live_content
content_served
-
Availability monitor · Recorded state
Unknown
probe_inconclusive
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
j62q.vip detected and queued for full analysis
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
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.
VirusTotal
18/91 recorded on VirusTotal
OTX Community References
5 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Brand Impersonation
Impersonation of Bet365
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Sent Report Recorded
Stored outgoing record associated with registrar NameMart Pte. Ltd., 1 abuse contact
abuse@namemart.com
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Monitoring Continues
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
urlscan.io
Screenshot · DOM · HTTP
Capture the rendered page, requests and visible infrastructure.
VirusTotal
Multi-engine verdicts
Compare the available engine results and retain the analysis timestamp.
Google Safe Browsing
Transparency Report
Check whether Google currently lists the URL as unsafe.
Cloudflare Radar
DNS · certificates · categories
Inspect a public scan and its recorded network and classification data.
AlienVault OTX
Threat-intelligence pulses
Look for indicator references and related community intelligence.
Wayback Machine
Historical evidence
Compare archived captures and preserve historical context.
abuse.ch ThreatFox
IOC correlation
Look for matching indicators and associated threat records.
crt.sh
Certificate Transparency
Inspect certificate records and related hostnames.
DNS Security Filters
Quad9 · AdGuard · CleanBrowsing
Compare security resolver responses and record observed blocking.
Web-Check
Surface inspection
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.
GoogleSafe Browsing↗
GoogleWeb Risk↗
MicrosoftSmartScreen↗
VirusTotalURL analysis↗
CloudflareRadar / abuse reporting↗
YandexSafe Browsing↗
URLScan.ioPublic scan↗
ESETSample / URL submission↗
BitdefenderURL submission↗
NortonSafe Web↗
SymantecSiteReview↗
AviraURL reporting↗
Avast / AVGURL reporting↗
KasperskyOpenTIP↗
Dr.WebOnline scanner↗
NetcraftAbuse reporting↗
PhishTankCommunity reporting↗
APWG eCXPhishing intelligence↗
PhishStatsPublic feed↗
Phish.ReportHosting abuse↗
SpamhausDomain reputation↗
PolySwarmMulti-engine analysis↗
CheckPhishURL scan↗
QutteraMalware scan↗
URLqueryBrowser analysis↗
Criminal IPAsset intelligence↗
CRDFThreat Center↗
ScamadviserReputation check↗
MyWOTCommunity reputation↗
Related infrastructure
Shared hosting, registrar records and related domains
Related Infrastructure & Reports
- 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.
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 matches 8
Same favicon hash or the same page title as this host.
Shared IP 154.39.104.138 6
Multiple reports share this IP.
Bet365 impersonation 8
These domains also target Bet365 users. View all Bet365 threats →
Same registrar: NameMart 6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
Evidence & investigation tools
Original reports, independent checks and evidence links
Evidence & External Reports
Security Analysis
Submitted Evidence Snapshot
Sent: Ledger records: 1
Case ID:
PD-20260717-FCFB10 Recipient: abuse@namemart.com Page title stored with report: welcome-BET365
Notice text archived (605 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 (CN): Cybersecurity Law of China Criminal Law Article 285 Criminal Law Article 266 - Fraud Chinese law strictly prohibits cyber fraud and illegal access to computer systems. 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.
OSINT & Intelligence
DNS & Network
SEO & Domain
Deep Analysis
Help & reporting
Recovery steps, reporting contacts and complaint drafts
Help & reporting
Were You Affected by This Site?
7 evidence signal groups linked
1 stored notification records
Last 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.
Official reporting routes
Action Fraud
Report online
Report fraud and cybercrime in England, Wales and Northern Ireland
Contact centre0300 123 2040
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
97-country directory
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
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
UrgentStop using the suspicious site. Open the real service through its official app or an address you already trust.
- Change all passwords — email, exchange accounts, anything that shares the same password
- Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
- Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelinesKeep 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.
- Exact dates & times — of each transaction and first contact with scammer
- Screenshots — scam website, chat messages, emails, wallet transactions, social media
- All URLs & domains used by the scammer (including
j62q.vip) - Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
- FBI IC3 — Internet Crime Complaint Center (US federal reporting)
- Europol — European cybercrime reporting (EU)
- Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
- Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
- Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Bookmark official sites — never click links from emails, DMs, or ads
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
About This Report: j62q.vip
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “welcome-BET365”. Apparent target: Bet365.
VirusTotal detections for j62q.vip: 18 (2026-09-29 02:12:13 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.