VirusTotal
17 / 92 engine detections
Open reportbzpxon.com is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Google LLC. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.
17 / 92 engine detections
Open report2 community references
Open reportScan report
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 bzpxon.com to its internal blocklist on 2026-10-23 as a suspicious domain based on aggregated security signals. The site returned HTTP 200 for the root URL on the same day, but no page title was recorded.
The domain is flagged because many anti‑malware engines label it as phishing or malware, which is typical of sites that may host deceptive content or drive‑by downloads. No specific malicious behavior was observed in the captured page snapshot.
VirusTotal scanned the domain on 2026-10-20 and reported 17 detections from 92 engines, with 15 malicious and 2 suspicious labels. Google Safe Browsing checked on 2026-10-23 and did not flag the domain. URLScan captured a snapshot on 2026-10-10 and returned a clean overall verdict with a neutral score. OTX listed two pulses referencing bzpxon.com as of 2026-10-23. PhishDestroy’s internal list includes the domain, while external blocklists checked on 2026-10-23 showed zero matches. Cloudflare Radar independently marked the domain as malware, reflecting its own assessment.
The domain was registered on 2025-04-23 through Dynadot Inc and uses the nameservers ns1.dyna-ns.net and ns2.dyna-ns.net. DNS resolution on 2026-10-20 returned an A record pointing to 34.8.229.132, an address owned by Google LLC in the United States. A Let’s Encrypt certificate issued on 2026-07-24 was valid until 2026-10-22.
Avoid entering credentials or downloading files from bzpxon.com. If any personal data was submitted, change the associated passwords and monitor accounts for unusual activity. Defenders should block the exact domain (bzpxon.com) at the network perimeter and review logs for connections to the recorded IP address.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a1239f-7cce-74dc-b973-68033545be06 |
|---|---|
| Final url | https://www.bzpxon.com/ |
| Globals | [
"assert",
"getRequiredElement",
"P",
"S",
"getRandomNum",
"getTimeStamp",
"Dimensions",
"Config$2",
"getGlobalConfig",
"setGlobalConfig",
"Config$1",
"Config",
"setMaxGapCoefficient",
"setMaxObstacleLength",
"Status",
"A11yStrings",
"RunnerClasses",
"RunnerSounds",
"RunnerEvents",
"updateCanvasScaling",
"getA11yString",
"vibrate",
"createCanvas",
"decodeBase64ToArrayBuffer",
"createAdjustedCollisionBox",
"drawCollisionBoxes",
"boxCompare",
"toggleHelpBox",
"diagnoseErrors",
"portalSignin",
"updateForDnsProbe",
"getMainFrameErrorCssClass",
"getMainFrameErrorIconCssClass",
"getSubFrameErrorIconCssClass",
"shouldShowSuggestionsSummaryList",
"getSuggestionsSummaryItemCssClass",
"reloadButtonClick",
"downloadButtonClick",
"detailsButtonClick",
"setAutoFetchState"
] |
| Domain age days | 534 |
| Apex age days | 1333 |
| Requests | 5 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": -46,
"malicious": false
},
"overall": {
"score": 0,
"malicious": false
}
} |
Observed: · Retrieved:
| Uuid | 5ef58f4a-07da-4469-9ae5-32f69e97f690 |
|---|---|
| Final url | https://bzpxon.com/ |
| History | [
{
"url": "https://bzpxon.com/",
"status": 0
}
] |
| DOM structure hash | 94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219 |
| Domain risks | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "bzpxon.com",
"type": "A",
"value": "34.8.229.132"
}
] |
| Dnssec valid | false |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2025-04-23T01:26:45Z",
"updated": "2026-06-02T01:28:04Z",
"expires": "2027-04-23T01:26:45Z",
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 43,
"malicious": 15,
"suspicious": 2,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"DNS8": "suspicious",
"ESET": "phishing",
"VIPRE": "malware",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Fortinet": "malware",
"SOCRadar": "phishing",
"Kaspersky": "phishing",
"Seclookup": "malicious",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"Chong Lua Dao": "malicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Categories | {
"alphaMountain.ai": "Phishing, Pornography (alphaMountain.ai)"
} |
| Created | 2025-04-23T00:00:00Z |
| Updated | 2026-04-23T00:00:00Z |
| First seen | 2024-08-19T10:44:02Z |
| DNS records | [
{
"ttl": 300,
"type": "NS",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "NS",
"value": "ns2.dyna-ns.net"
},
{
"ttl": 300,
"type": "SOA",
"rname": "hostmaster.bzpxon.com",
"value": "ns1.dyna-ns.net"
},
{
"ttl": 300,
"type": "A",
"value": "34.8.229.132"
}
] |
| Dns at | 2026-10-20T00:09:23Z |
| Jarm | 29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84 |
| Certificate | {
"san": [
"bzpxon.com"
],
"issuer": "Let's Encrypt / YR2",
"serial": "63c357208cbfd7144821426b5c51e94c6e4",
"sha256": "fe94b81f3f0fe4106315acf1074672c0dbf977cf20f3678058c4c92a6725b61c",
"subject": "bzpxon.com",
"valid_to": "2026-10-22T06:30:06Z",
"valid_from": "2026-07-24T06:30:07Z"
} |
| Registry data | {
"status": [
"transfer prohibited"
],
"events": {
"expiration": "2027-04-23T01:26:45Z",
"last changed": "2026-07-24T06:23:16Z",
"registration": "2025-04-23T01:26:45Z",
"registrar expiration": "2027-04-23T01:26:45Z",
"last update of RDAP database": "2026-10-16T07:01:26Z"
},
"registrar": "DYNADOT LLC",
"registrar_iana_id": "472"
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "bzpxon.com"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-16T05:22:18Z",
"first": "2025-07-10T23:32:07Z",
"changes": 2,
"days_archived": 3,
"scans_per_day": 0,
"avg_page_bytes": 8970
} |
| Ports | {
"open": [
80,
443
]
} |
| Dns server | {
"ns": [
{
"ip": "162.159.27.158",
"host": "ns1.dyna-ns.net"
},
{
"ip": "162.159.24.5",
"host": "ns2.dyna-ns.net"
}
],
"zone": "bzpxon.com"
} |
| Location | {
"ip": "34.8.229.132",
"asn": "396982",
"org": "Google LLC",
"city": "Kansas City",
"country": "US"
} |
| DNS records | {
"A": [
"34.8.229.132"
],
"NS": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
],
"SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.bzpxon.com\", \"serial\": 2026072301, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Get ip | {
"ip": "34.8.229.132",
"family": 4
} |
| Registration record | {
"registrar": "Dynadot Inc",
"created": "2025-04-23T01:26:45Z",
"updated": "2026-06-02T01:28:04Z",
"expires": "2027-04-23T01:26:45Z",
"status": [
"clientTransferProhibited https://icann.org/epp"
],
"nameservers": [
"ns1.dyna-ns.net",
"ns2.dyna-ns.net"
]
} |
No. PhishDestroy classifies bzpxon.com 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 bzpxon.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.
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
fe94b81f3f0fe4106315acf1074672c0dbf977cf20f3678058c4c92a6725b61cbzpxon.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bzpxon.com/Server: nginxContent-Type: text/html; charset=utf-8Content-Encoding: gzipgziptext/html; charset=utf-8Fri, 23 Oct 2026 20:16:32 GMT0.0076620579nginxchunkedAccept-Encoding1.1 googleValues retained by the collector; long values may be shortened during collection.
2 community references
View sourceNo threat flag
View source17/92 engine detections
View sourcebzpxon.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
bzpxon.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 ↗
bzpxon.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.