VirusTotal
18 / 89 engine detections
Open reportbilitage.digital is a crypto investment scam detected by PhishDestroy on 2026-09-07. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Snel.com B.V. PhishDestroy sent 1 abuse report. VirusTotal: 18/89 engines flag it. Do not enter credentials or connect a wallet.
“bilitage | AI Trading Platform | Official Website”
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; 1 month 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.
18 / 89 engine detections
Open report4 threat-system alerts
Open reportMalicious
Open report5 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | bilitage.digital |
malicious | Sinkholed |
| DNS4EU | bilitage.digital |
malicious | Sinkholed |
| Quad9 DNS | bilitage.digital |
malicious | Sinkholed |
| Cloudflare DNS | bilitage.digital |
malicious | Sinkholed |
PhishDestroy threat report
bilitage.digital presents itself as a legitimate cryptocurrency trading service called Bilitage, marketing an AI-powered trading platform to retail investors seeking automated returns. PhishDestroy first flagged it on 2026-09-07, less than three months after the domain was created. As of 2026-10-19 the domain remains alive, though its content is currently unreachable.
Fake exchange scams lure victims by promising superior, often algorithmically driven profits, persuading them to register and deposit cryptocurrency. The page title 'bilitage | AI Trading Platform | Official Website' uses the word 'Official' to project legitimacy and the AI angle to justify implausible returns. Once funds are deposited, the platform either blocks withdrawals outright or invents tax, fee or verification requirements that must be paid before any balance can be released — money that was never traded in the first place. Because cryptocurrency transactions are irreversible, deposited funds are unrecoverable.
Eighteen of 89 engines on VirusTotal flagged this domain as malicious as of 2026-09-18, with detections from BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, CRDF, CyRadar, alphaMountain.ai and Chong Lua Dao, among others. Five independent threat-intelligence pulses on AlienVault OTX confirm that multiple research teams beyond PhishDestroy have identified this domain as harmful. It appears on the PhishDestroy blocklist.
The domain was registered on 2026-06-25 through Dynadot Inc, giving it a lifespan of under three months before detection. It is hosted on IP 185.62.58.129 within the Snel.com B.V. network in the Netherlands. TLS is provided by ZeroSSL GmbH via its ECC DV SSL CA 2, a free automated certificate that requires no identity verification from the site operator.
If you deposited cryptocurrency here, treat those funds as unrecoverable and do not send further amounts in response to any fee, tax or verification demands. If you submitted identity documents or payment card details, notify your bank and report the incident to your national financial regulator. Be alert to follow-up contact offering fund recovery, as secondary scams routinely target the same victims. Security teams should block bilitage.digital at the DNS and firewall level and pull the AlienVault OTX pulse data into their threat-intelligence pipelines.
No. PhishDestroy classifies bilitage.digital as a crypto investment scam (risk: critical, 100/100); it was first detected on 2026-09-07. VirusTotal: 18/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on bilitage.digital. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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.
kevin.ns.cloudflare.comsarah.ns.cloudflare.comLocation describes the IP network.
33709a8031a058cd7a1e9ecde1b706ac378566114a66e68d71d632485dd92316bilitage.digitalSaved 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 bilitage.digital · checked Sep 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a07d87-6e31-7476-944c-c2bae1857388 |
|---|---|
| Final url | https://bilitage.digital/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://bilitage.digital/",
"from": "http://bilitage.digital/",
"status": 307
}
] |
| Ip | 185.62.58.129 |
| Ptr | static-129-58-62-185.hosted-by-snel.com |
| Contacted domains | [
"cdn.jsdelivr.net",
"cdnjs.cloudflare.com",
"fonts.gstatic.com",
"www.cloudflare.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"104.17.207.5",
"104.16.124.96",
"192.178.183.94",
"2606:4700::6811:cf05",
"104.17.24.14",
"2a00:1450:4001:c15::5f",
"185.62.58.129"
] |
| Asns | [
"13335",
"15169",
"62370"
] |
| Countries | [
"US",
"DE",
"NL"
] |
| Document hash | c447f201a0a847ef291c71d1759141aa0b090e4fe43e6a01f8ac5b77cd9cd55e |
| Script hashes | [
"dcffb692e1e6bda024f7830b7f5a3fa758c06ede0ac195daebf2c9fe01442f3f"
] |
| Globals | [
"toggleTermsPopup",
"intlTelInput",
"__visitorCountry",
"ClientJS"
] |
| Storage keys | [
"t_cfp"
] |
| Tls | {
"san": [
"bilitage.digital"
],
"cipher": "AES_128_GCM",
"issuer": "ZeroSSL ECC DV SSL CA 2",
"subject": "bilitage.digital",
"protocol": "TLS 1.3",
"valid_to": "2026-10-25T23:59:59Z",
"valid_from": "2026-07-27T00:00:00Z"
} |
| Domain age days | 74 |
| Apex age days | 74 |
| Tls age days | 42 |
| Tls valid days | 90 |
| Requests | 20 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"referrer-policy": "no-referrer-when-downgrade"
} |
Observed: · Retrieved:
| Uuid | f01479b5-026a-492d-ade0-b157c183ea01 |
|---|---|
| Final url | https://bilitage.digital/ |
| Status | 200 |
| History | [
{
"url": "https://bilitage.digital/",
"status": 200
}
] |
| DOM structure hash | 7f816f587042463af878b6b1002d2e020a8989888c085952faa743272f45fe84 |
| Document hash | c447f201a0a847ef291c71d1759141aa0b090e4fe43e6a01f8ac5b77cd9cd55e |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "bilitage.digital",
"type": "A",
"value": "185.62.58.129"
}
] |
| Dnssec valid | false |
| Ip | 185.62.58.129 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 43,
"malicious": 14,
"suspicious": 3,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "suspicious",
"ESET": "suspicious",
"VIPRE": "malware",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "phishing",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| First seen | 2026-06-25T08:53:50Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "sarah.ns.cloudflare.com"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "kevin.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "185.62.58.129"
},
{
"ttl": 21600,
"type": "NS",
"value": "kevin.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-21T14:20:59Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"bilitage.digital"
],
"issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
"serial": "850bbe527eba0f1abc230b4b2a3b40b9",
"sha256": "33709a8031a058cd7a1e9ecde1b706ac378566114a66e68d71d632485dd92316",
"subject": "bilitage.digital",
"valid_to": "2026-12-24T23:59:59Z",
"valid_from": "2026-09-25T00:00:00Z"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-06-25T06:58:08Z",
"last changed": "2026-06-25T07:41:28Z",
"registration": "2026-06-25T06:58:08Z",
"registrar expiration": "2027-06-25T06:58:08Z",
"last update of RDAP database": "2026-10-16T07:18:43Z"
},
"registrar": "DYNADOT LLC",
"registrar_iana_id": "472"
} |
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
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
17→18
Reachable
5 community references
View sourceNo threat flag
View source18/89 engine detections
View sourcePD-20260907-ABF99E
bilitage.digital
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bilitage.digital
PD-20260907-ABF99E 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
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Select 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 ↗
bilitage.digital)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
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.