Skip to security report
Analytics Dashboard
Domain security report
j105m.vip favicon

j105m.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 Automated brand label: Bet365
OTX: 5 refs Jul 2, 2026 Bet365
API
Registrar
NameMart
Resolved IP
103.244.148.113
Registered
Jun 26, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
18 det.
OTX references
5 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Hostname mismatch
Let's Encrypt · Certificate hostname mismatch
Age
4 mo
Observed status
Last known active 200
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

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.

VirusTotal

18 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

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

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

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.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & 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

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
18/91
OTX
5 community refs
URLScan
Stored capture

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 j105m.vip is currently active and returns HTTP status code 200 when queried. Registration records show it was created through NameMart Pte. Ltd., and the authoritative name servers are ns1.1111343.com, ns2.1111343.com, ns3.1111343.com, and ns4.1111343.com. VirusTotal analysis indicates that 19 of 91 security vendors have classified the domain as malicious, supporting a high‑risk assessment.

The domain is listed on a single public security blocklist and is actively blocked by the PhishDestroy filtering service. No additional intelligence such as Safe Browsing verdicts, OTX references, SSL certificate details, or hosting IP information is available in the current dataset, leaving the exact content and infrastructure footprint of the site unconfirmed. Analysts should treat the domain as a confirmed phishing vector given the vendor detections and blocklist presence.

Defensive actions include adding j105m.vip to internal DNS and proxy blocklists, monitoring for any resolution to new IP addresses, and employing sinkholing or traffic redirection where feasible. Continuous re‑evaluation is advised to capture any changes in hosting, page content, or additional vendor detections that may emerge as the campaign evolves.

Data coverage & collection

18 · datasets with records / 13 · 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
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
5 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
NameMart Pte. Ltd.Collection time not recorded
Network & DNS
103.244.148.113 · 4 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Availability history
30 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 13

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

NameMart Pte. Ltd. · 103.244.148.113 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 24, 2026
OTX tags 2026-07activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar NameMart SG(SG)
Abuse contact["abuse@namemart.com", "support@namemart.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for j105m.vip →
RegistrationCreated Jun 26, 2026 (113d) — Expires Jun 26, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJul 2, 2026
DOM Analysisanalyzed Jul 29, 2026score 98/1001 brand signal
Submitted URLhttp://j105m.vip/
Favicon Hash
ICANN OVERSIGHT

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
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
103.244.148.113
Network ASN
AS135357
Organization
Shenzhenshihong Technology Development Co., Ltd
Observed location
Hong Kong, HK
Server header
Nginx
Nameservers 4
  • ns1.1111343.com
  • ns2.1111343.com
  • ns3.1111343.com
  • ns4.1111343.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-05 09:41:06
Valid until
2026-10-03 09:41:05
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-07-26 16:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8a7b9ec40848a1645ebc3f6f380c623d14498254fc792d1b17b7bbb1dbdc4cd3
Certificate names · 95 SANs
  • b40e.top
  • b40s.top
  • b40t.top
  • b41i.top
  • b41j.top
  • f36l.top
  • f36n.top
  • f36o.top
  • h30e.top
  • h30g.top
  • h30m.top
  • h30n.top
  • h30o.top
  • j101y.vip
  • j101z.vip
  • j105b.vip
  • j105c.vip
  • j105f.vip
  • j105g.vip
  • j105h.vip
  • j105i.vip
  • j105j.vip
  • j105k.vip
  • j105n.vip
  • j105o.vip
  • j105p.vip
  • j105q.vip
  • j105r.vip
  • j105s.vip
  • j105t.vip
  • j105u.vip
  • j105v.vip
  • j105w.vip
  • j105x.vip
  • m26p.top
  • p33t.top
  • p33u.top
  • p33y.top
  • p33z.top
  • s33t.top
  • s33u.top
  • s33v.top
  • s33x.top
  • s33y.top
  • s35n.top
  • s35o.top
  • s35p.top
  • www.b40e.top
  • www.b40s.top
  • www.b40t.top
  • www.b41i.top
  • www.b41j.top
  • www.f36l.top
  • www.f36n.top
  • www.f36o.top
  • www.h30e.top
  • www.h30g.top
  • www.h30m.top
  • www.h30n.top
  • www.h30o.top
  • www.m26p.top
  • www.p33t.top
  • www.p33u.top
  • www.p33y.top
  • www.p33z.top
  • www.s33t.top
  • www.s33u.top
  • www.s33v.top
  • www.s33x.top
  • www.s33y.top
  • www.s35n.top
  • www.s35o.top
  • www.s35p.top
  • www.u26s.top
  • www.u26t.top
  • www.x29v.top
  • www.x29w.top
  • www.x29x.top
  • www.x31b.top
  • www.x31c.top
  • www.x31d.top
  • www.x31k.top
  • www.x31l.top
  • www.x31m.top
  • www.y37e.top
  • x29v.top
  • x29w.top
  • x29x.top
  • x31b.top
  • x31c.top
  • x31d.top
  • x31k.top
  • x31l.top
  • x31m.top
  • y37e.top

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 103.244.148.113rapiddns.io

Latest Classified Outcome 2026-10-17 10:19:02 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:02 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:19:02 UTC last content: 2026-10-17 10:19:02 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
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: 20 detections
alphaMountain.ai
BitDefender
Certego
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

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.
  1. Threat First Observed 2026-07-26 15:23:09 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 103.244.148.113.
Stored observation history31

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 26
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    live_content→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
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
j105m.vip detected and queued for full analysis
Jul 2, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
Sep 25, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jul 26, 2026
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Jul 26, 2026
VirusTotal
18/91 recorded on VirusTotal
Sep 27, 2026
OTX Community References
5 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
Brand Impersonation
Impersonation of Bet365
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Jul 26, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Jul 2, 2026
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.

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.

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
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts
Official reporting routes
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
After a phishing incident

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?

Urgent

Stop 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 guidelines

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.
  • 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 j105m.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 Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: j105m.vip

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “welcome-BET365”. Apparent target: Bet365.

VirusTotal detections for j105m.vip: 18 (2026-09-27 02:25:58 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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/j105m.vip"
  title="PhishDestroy threat report for j105m.vip"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>