dxsz.bid is registered with whois.nic.bid and is hosted on AS209242 CloudFlare London LLC in United States of America. Its SSL certificate from Sectigo Limited expired on 27 Sept 2025, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is dxsz.bid’s name taken on other extensions?
Every IP address dxsz.bid resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| dxsz.bid | 23.145.136.206 | 260 |
| dxsz.bid | 23.145.136.207 | 260 |
| dxsz.bid | 23.145.136.208 | 260 |
| Host | Name server | TTL |
|---|---|---|
| dxsz.bid | dayana.ns.cloudflare.com | 21600 |
| dxsz.bid | terry.ns.cloudflare.com | 21600 |
| Host | Start of authority | TTL |
|---|---|---|
| dxsz.bid | dayana.ns.cloudflare.com dns.cloudflare.com 2367600413 10000 2400 604800 1800 | 1800 |
Other domains served from 23.145.136.206. Normal for shared hosting and CDNs.
No reviews yet. Used dxsz.bid? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
dxsz.bid has no community safety rating yet. Its SSL certificate expired on 27 Sept 2025. See Security →
dxsz.bid is registered through whois.nic.bid. See WHOIS →
dxsz.bid is served from 3 IP addresses, mainly on AS209242 CloudFlare London LLC in United States of America. See Hosting →
Raw registry data for dxsz.bid. May be redacted by privacy services.
Number of allowed queries exceeded.
The first response from http://www.dxsz.bid, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with dxsz.bid. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.