VirusTotal
11 / 92 engine detections
Open reportcryptobondora.com is a MetaMask impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (100/100). Registrar: Realtime. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 11/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“OnchainCrypto - Trading, for everyone”
11 / 92 engine detections
Open reportDBL_PHISH
5 community references
Open reportprovider verdict: clean
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.
PhishDestroy threat report
cryptobondora.com is an impersonation phishing page that presents itself as "OnchainCrypto - Trading, for everyone", a retail crypto trading service. It targets people looking for an easy way to trade crypto who may trust a polished, brand-styled front end. PhishDestroy first flagged it on 2026-10-11. As of 2026-10-19 the site was still online and serving its content.
Impersonation pages like this copy the look and promise of a legitimate trading platform so visitors drop their guard. A "trading for everyone" pitch is typically used to steer victims into signing up, handing over login details, connecting a wallet, or depositing funds into an account they never actually control. Whatever goes in, whether credentials, wallet authorizations or deposited crypto, ends up with the operators, and crypto transfers are effectively irreversible.
On 2026-10-16, 11 of 92 VirusTotal engines flagged the domain, including Kaspersky, BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a modest share, but the mix of vendors is broad. Spamhaus lists it in its domain blocklist with a phishing tag. MetaMask and SEAL both block it alongside PhishDestroy, which means the wallet and security communities have independently judged it a threat. It also appears in five AlienVault OTX threat pulses.
The domain was registered on 2026-08-13 through Realtime Register B.V., about two months before PhishDestroy caught it. That gap is consistent with a site that was set up and allowed to sit for a while before being pushed to victims. It is served from Amazon's network with a Swedish IP location, and its certificate was issued by Amazon. This shows it is fronted by mainstream cloud infrastructure, so a padlock and fast loading say nothing about legitimacy.
Do not log in, deposit or connect a wallet on this site. If you entered a password, change it everywhere you reused it and turn on app-based 2FA. If you sent funds, stop all further payments and ignore any "fee" or "verification" request promised to unlock withdrawals. If you connected a wallet, review and revoke any token approvals, and move remaining assets to a fresh wallet if you shared a seed phrase. Defenders should block the domain at DNS and proxy level and report it to the registrar and hosting provider.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0a94e-1b5b-71ca-8be8-532201593e85 |
|---|---|
| Final url | https://cryptobondora.com/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://cryptobondora.com/",
"from": "http://cryptobondora.com/",
"status": 307
}
] |
| Ip | 172.67.199.109 |
| Contacted IP addresses | [
"172.67.199.109"
] |
| Asns | [
"13335"
] |
| Document hash | a35953fcf70b1acdba514c82b3a0bb5c1606b7bd017af699325931f685ea4130 |
| Script hashes | [
"fdc1b7473ac0b3c05bd6a0b24e7494fe3cd9dedd7a8a00377e9082eab295b365",
"8554254d35f9a73c406b2426380f089017c0f62c913cd34870a7f780d44671da",
"8842dadb21e281fc560d6ad7d6205179f7095fe0510ddf9f38bbf9c66a085b52",
"6d6631d9377354eefc3697889d2cb39c4aef1edc1db8090f63732e921996dcf3",
"7c581264b053bf727edcad45dcb99abcf7ea60313d79768da0925d3b9492745a",
"b56d39dccc19df635b4343b1d8fc58006b0a8e30f1a302e070ce4f1baf5d1927",
"9e36618d469a8b3360792dd3e3bb65f2f651f08ab049b4be565002583d0b62ef",
"32396b455a98370e17f53cbab4ef81bb52b29c26b0f85f882bfec89a1bef6160",
"a75edab4f18721c67ca0681d90114acca5b330e47699a3a7adc144fe47a67245",
"ec83135dd9055b05879d2fb52aec84a6e782ab5de7791692cef280500c3f24db"
] |
| Globals | [
"__APP_CONFIG__"
] |
| Cookies | [
"XSRF-TOKEN",
"laravel_session"
] |
| Storage keys | [
"lang",
"device_fingerprint"
] |
| Tls | {
"san": [
"cryptobondora.com",
"*.cryptobondora.com"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "cryptobondora.com",
"protocol": "QUIC",
"valid_to": "2026-11-11T07:12:21Z",
"valid_from": "2026-08-13T06:13:38Z"
} |
| Domain age days | 33 |
| Apex age days | 33 |
| Tls age days | 34 |
| Tls valid days | 90 |
| Requests | 65 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | 9ba30d02-6f3d-4aa8-8213-96f66fbf4705 |
|---|---|
| Final url | https://cryptobondora.com/ |
| Status | 200 |
| History | [
{
"url": "https://cryptobondora.com/",
"status": 200
}
] |
| DOM structure hash | 2969cdb501557983d7a085de18f508265d9ddb87fe21f8118c9c637bc0a67ff2 |
| Document hash | a35953fcf70b1acdba514c82b3a0bb5c1606b7bd017af699325931f685ea4130 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "cryptobondora.com",
"type": "A",
"value": "52.85.129.120"
},
{
"name": "cryptobondora.com",
"type": "A",
"value": "52.85.129.115"
},
{
"name": "cryptobondora.com",
"type": "A",
"value": "52.85.129.121"
},
{
"name": "cryptobondora.com",
"type": "A",
"value": "52.85.129.124"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:c00:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:7800:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:e000:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:2e00:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:d000:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:1000:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:ae00:9:a709:2700:93a1"
},
{
"name": "cryptobondora.com",
"type": "AAAA",
"value": "2600:9000:2004:4400:9:a709:2700:93a1"
}
] |
| Dnssec valid | false |
| Ip | 52.85.129.120 |
| Registration record | {
"registrar": "Realtime Register B.V.",
"created": "2026-08-13T00:58:27Z",
"updated": "2026-10-12T01:08:52Z",
"expires": "2027-08-13T00:58:27Z",
"nameservers": [
"dax.ns.cloudflare.com",
"magnolia.ns.cloudflare.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 0,
"suspicious": 0,
"undetected": 37
} |
|---|---|
| Reputation | 0 |
| Registrar | Realtime Register B.V. |
| Created | 2026-08-13T00:58:27Z |
| Expires | 2027-08-13T00:58:27Z |
| Updated | 2026-10-12T01:08:52Z |
| First seen | 2026-08-13T07:56:53Z |
| DNS records | [
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:6600:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:6000:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "A",
"value": "3.161.174.82"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "dax.ns.cloudflare.com"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:b200:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:be00:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:9200:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:d800:9:a709:2700:93a1"
},
{
"ttl": 21600,
"type": "NS",
"value": "dax.ns.cloudflare.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "magnolia.ns.cloudflare.com"
},
{
"ttl": 60,
"type": "A",
"value": "3.161.174.26"
},
{
"ttl": 60,
"type": "A",
"value": "3.161.174.94"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:fe00:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "AAAA",
"value": "2600:9000:200e:dc00:9:a709:2700:93a1"
},
{
"ttl": 60,
"type": "A",
"value": "3.161.174.56"
}
] |
| Dns at | 2026-10-20T16:09:34Z |
| Jarm | 29d29d00029d29d00041d41d00041db78309d03c04b7072bacbf1ce396279b |
| Certificate | {
"san": [
"cryptoflowen.com",
"cryptoliquivault.com",
"cryptoequiflow.com",
"cryptotreasora.com",
"cryptoreturnix.com",
"equitynexora.com",
"cryptobondex.com",
"cryptobondora.com",
"cryptosafutrade.com",
"alphavestora.com"
],
"issuer": "Amazon / Amazon RSA 2048 M01",
"serial": "e9c1a34827415a96c05c91684c84e87",
"sha256": "fbd0513ce8682dd47be4c87b0ae5a82afe8b4106c675752d5c82eea42c6b9463",
"subject": "cryptoflowen.com",
"valid_to": "2027-04-07T23:59:59Z",
"valid_from": "2026-09-22T00:00:00Z"
} |
| Registration record | {
"registrar": "Realtime Register B.V.",
"registrar_iana_id": "839",
"registrar_url": "http://www.realtimeregister.com",
"created": "2026-08-13T00:58:27Z",
"updated": "2026-10-12T01:08:52Z",
"expires": "2027-08-13T00:58:27Z",
"status": [
"ok"
],
"nameservers": [
"dax.ns.cloudflare.com",
"magnolia.ns.cloudflare.com"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"active"
],
"events": {
"expiration": "2027-08-13T00:58:27Z",
"last changed": "2026-10-12T01:08:53Z",
"registration": "2026-08-13T00:58:27Z",
"registrar expiration": "2027-08-13T00:58:27Z",
"last update of RDAP database": "2026-10-20T16:09:34Z"
}
} |
No. PhishDestroy classifies cryptobondora.com as a MetaMask impersonation page (risk: critical, 100/100); it was first detected on 2026-10-11. VirusTotal: 11/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on cryptobondora.com. 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.
Last checked
Edge-IP reputation is not attributed to this domain.
magnolia.ns.cloudflare.comLocation describes the IP network.
fbd0513ce8682dd47be4c87b0ae5a82afe8b4106c675752d5c82eea42c6b9463alphavestora.comcryptobondex.comcryptoequiflow.comcryptoflowen.comcryptoliquivault.comcryptoreturnix.comcryptosafutrade.comcryptotreasora.comequitynexora.comSaved 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 cryptobondora.com · checked Oct 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
No threat flag
View source11/92 engine detections
View source5 community references
View sourcecryptobondora.com
View source79 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
cryptobondora.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 ↗
cryptobondora.com)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.