VirusTotal
17 / 92 engine detections
Open reportbitqttrade.net is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Omegatech LTD. PhishDestroy sent 1 abuse report. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.
“Bitqt”
17 / 92 engine detections
Open report3 det.
Open reportMalicious
Open report5 community references
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy added bitqttrade.net to its internal blocklist after automated analysis flagged the site as suspicious. The recorded page title was “Bitqt”. The domain was first seen by PhishDestroy on 2026-10-23 and returned an HTTP 200 response on that date. No specific malicious behavior was observed in the page content.
The classification is based on the presence of multiple security‑vendor detections that commonly indicate phishing, malware distribution, or fraudulent financial services. No concrete mechanism such as credential capture or wallet interaction was observed on the page. Consequently, the listing reflects a general risk of a potentially deceptive crypto‑related service rather than a confirmed attack vector.
VirusTotal recorded 14 malicious and 3 suspicious detections from 92 engines on 2026-10-23 (analysis date 2026-10-17), totaling 17 detections. Google Safe Browsing checked on 2026-10-23 and did not flag the domain. urlscan.io’s engine verdict marked the site malicious with a score of 93 on 2026-10-23, while its overall verdict was neutral. Cloudflare Radar flagged the domain as malicious and categorized it under malware on 2026-10-23. OTX listed five pulses mentioning the domain as of 2026-10-23. PhishDestroy’s internal blocklist included the domain, whereas external blocklists returned zero hits on the same day.
The domain was registered with Dynadot Inc on 2026-06-24, giving it an age of about 120 days at the time of observation. The recorded IP was 158.94.210.119 and the associated network name was Omegatech LTD, located in the Netherlands. The certificate check found a Let's Encrypt certificate valid from 2026-09-11 to 2026-12-10 covering the apex and wildcard subdomains. The scan observed open ports 22, 80, and 443, and the authoritative nameservers were ns1.dyna-ns.net and ns2.dyna-ns.net.
Visitors should avoid entering credentials, cryptocurrency addresses, or personal data on the site; if any such information was submitted, change the associated passwords and monitor accounts for unusual activity. Security teams can add bitqttrade.net to their blocklists and review network logs for connections to the recorded IP 158.94.210.119. No wallet‑related remediation is advised because no wallet interaction was observed.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a167e6-3bcf-75a3-a2d0-dfd41b899287 |
|---|---|
| Final url | https://bitqttrade.net/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://bitqttrade.net/",
"from": "http://bitqttrade.net/",
"status": 307
}
] |
| Ip | 158.94.210.119 |
| Contacted IP addresses | [
"158.94.210.119"
] |
| Asns | [
"202412"
] |
| Countries | [
"NL"
] |
| Document hash | b788dd19cdd409563bc02099d15bea6d3936263cbc271908cfedfb7dade32242 |
| Script hashes | [
"8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
] |
| Globals | [
"__dclq",
"__dclOrig",
"__dclFlush",
"__smsCheckBeforeSubmit",
"__isSmsEnabled",
"__isSmsVerified",
"intlTelInput",
"navToggle",
"navMenu",
"langBtn",
"langDropdown"
] |
| Cookies | [
"connect.sid"
] |
| Tls | {
"san": [
"*.bitqttrade.net",
"bitqttrade.net"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "bitqttrade.net",
"protocol": "TLS 1.3",
"valid_to": "2026-12-10T13:48:10Z",
"valid_from": "2026-09-11T13:48:11Z"
} |
| Domain age days | 120 |
| Apex age days | 120 |
| Tls age days | 41 |
| Tls valid days | 89 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 93,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
} |
Observed: · Retrieved:
| Uuid | c38026d5-f7fe-41c3-9aca-14e89444d1e8 |
|---|---|
| Final url | https://bitqttrade.net/ |
| Status | 200 |
| History | [
{
"url": "https://bitqttrade.net/",
"status": 200
}
] |
| DOM structure hash | b3ef19008dff0fd4889872b774640a6fe9b5cf3f0d2aaa746990764bd8cb9e24 |
| Document hash | 3bd9a3db936e15ade35f9d79bf24391377932e3d5bf6acd9829562e257242a1d |
| Url risks | [
"Scam"
] |
| Domain risks | [
"Scam",
"Security threats",
"Malware",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "bitqttrade.net",
"type": "A",
"value": "158.94.210.119"
}
] |
| Dnssec valid | false |
| Ip | 158.94.210.119 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2026-06-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 43,
"malicious": 14,
"suspicious": 3,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"DNS8": "suspicious",
"ESET": "suspicious",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Fortinet": "phishing",
"Netcraft": "malicious",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrar | Dynadot Inc |
| Created | 2026-06-24T10:39:00Z |
| Expires | 2027-06-24T10:39:00Z |
| Updated | 2026-08-13T12:43:33Z |
| First seen | 2026-06-24T11:26:29Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "158.94.210.119"
},
{
"ttl": 300,
"type": "NS",
"value": "ns2.dyna-ns.net"
},
{
"ttl": 300,
"type": "SOA",
"rname": "hostmaster.bitqttrade.net",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "NS",
"value": "ns1.dyna-ns.net"
}
] |
| Dns at | 2026-10-17T11:51:27Z |
| Jarm | 40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319 |
| Certificate | {
"san": [
"*.bitqttrade.net",
"bitqttrade.net"
],
"issuer": "Let's Encrypt / YE1",
"serial": "57e8a56990ef7a6893376020c92432bd418",
"sha256": "b7d8c37a21d82f6ab1231b48e3bc05c6647049fa8d73e57b198760e7e0524bee",
"subject": "bitqttrade.net",
"valid_to": "2026-12-10T13:48:10Z",
"valid_from": "2026-09-11T13:48:11Z"
} |
| Registration record | {
"registrar": "Dynadot Inc",
"registrar_iana_id": "472",
"registrar_url": "http://www.dynadot.com",
"created": "2026-06-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-06-24T10:39:00Z",
"last changed": "2026-09-11T14:46:53Z",
"registration": "2026-06-24T10:39:00Z",
"registrar expiration": "2027-06-24T10:39:00Z",
"last update of RDAP database": "2026-10-16T07:18:29Z"
}
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "bitqttrade.net"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-23T08:38:53Z",
"first": "2026-10-07T11:57:58Z",
"changes": 1,
"days_archived": 2,
"scans_per_day": 0.06,
"avg_page_bytes": 18209
} |
| Crawler rules | {
"agents": [
"*"
],
"present": true,
"sitemaps": [
"https://bitqttrade.net/sitemap.xml"
]
} |
| Sitemap | {
"present": true,
"url_count": 5
} |
| Page title and metadata | {
"title": "Algorithmic Precision & Real-Time Insights | Bitqt",
"robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
"description": "For ambitious investors seeking smarter market moves: Bitqt offers an AI-Powered Trading Platform built to automate analysis and scale your crypto strategy globally.",
"canonicalUrl": "https://bitqttrade.net/"
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 283,
"tls": 93,
"wait": 87,
"connect": 69,
"download": 161
},
"response_ms": 693
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_128_GCM_SHA256",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
22,
80,
443
]
} |
| Carbon | {
"bytes": 95501,
"co2_grams": 0.0035,
"cleaner_than": 23
} |
| Dns server | {
"ns": [
{
"ip": "162.159.24.5",
"host": "ns2.dyna-ns.net"
},
{
"ip": "162.159.26.92",
"host": "ns1.dyna-ns.net"
}
],
"zone": "bitqttrade.net"
} |
| Location | {
"ip": "158.94.210.119",
"asn": "202412",
"org": "Omegatech LTD",
"city": "Amsterdam",
"country": "NL"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE1",
"subject": "bitqttrade.net"
} |
| DNS records | {
"A": [
"158.94.210.119"
],
"NS": [
"ns2.dyna-ns.net",
"ns1.dyna-ns.net"
],
"SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.bitqttrade.net\", \"serial\": 2026091102, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"message": "Site does not serve any HSTS headers."
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": "same-origin",
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": false,
"strictTransportPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "158.94.210.119",
"family": 4
} |
| Redirects | {
"chain": [
"https://bitqttrade.net"
]
} |
| Subdomains | {
"count": 1,
"subdomains": [
"www.bitqttrade.net"
]
} |
| Page links | {
"internal_count": 26
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2026-06-24T10:39:00Z",
"updated": "2026-08-13T12:43:33Z",
"expires": "2027-06-24T10:39:00Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
| HTTP headers | {
"headers": {
"content-type": "text/html; charset=utf-8",
"x-content-type-options": "nosniff",
"referrer-policy": "same-origin"
}
} |
No. PhishDestroy classifies bitqttrade.net as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on bitqttrade.net. 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.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
b7d8c37a21d82f6ab1231b48e3bc05c6647049fa8d73e57b198760e7e0524bee*.bitqttrade.netbitqttrade.netSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.bitqttrade.netDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bitqttrade.net · checked Oct 23, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bitqttrade.net/https://bitqttrade.net/Cache-Control: no-cache, no-store, must-revalidateContent-Encoding: gzipContent-Type: text/html; charset=utf-8X-Powered-By: Expressh3=":443"; ma=2592000no-cache, no-store, must-revalidategzip416text/html; charset=utf-8Fri, 23 Oct 2026 08:39:40 GMTsame-originAccept-Encoding1.1 CaddynosniffExpressValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy
bitqttrade.net
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
5 community references
View sourceNo threat flag
View source17/92 engine detections
View sourcePD-20261023-E2020A
bitqttrade.net
View sourcePage captured
View sourcePD-20261023-E2020A Recipient: abuse@omegatech.sc 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.
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 ↗
bitqttrade.net)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.