xbiquge.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 41 days left10 years old
50
xbiquge.cc was registered on 16 Dec 2015 via GoDaddy.com, LLC and the registry expiry is 16 Dec 2026. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
xbiquge.cc publishes 3 nameservers. DNSSEC is not signed.
xbiquge.cc has 1 IPv4 address (162.209.201.221). The geolocation database places 162.209.201.221 in Los Angeles (Downtown Los Angeles), United States.
The TLS certificate from YE2 is valid and has 41 days left (TLS 1.3).
No safety warning was recorded for xbiquge.cc in the checks that ran.
Domain · RDAP/WHOIS
xbiquge.cc was registered on 16 Dec 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 3 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
| Registered | since 16 Dec 2015 |
|---|---|
| Created | 16 December 2015 |
| Updated | 22 October 2026 |
| Expires | 16 December 2026 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | a.dnspod.com, b.dnspod.com, c.dnspod.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc |
xbiquge.cc carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
xbiquge.cc carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
xbiquge.cc carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
xbiquge.cc carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver a.dnspod.com is published for xbiquge.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
Nameserver b.dnspod.com is published for xbiquge.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
Nameserver c.dnspod.com is published for xbiquge.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
DNS
xbiquge.cc has 1 address record, 0 mail exchangers and 3 nameservers, measured at 1.1.1.1:53.
| A | 162.209.201.221 |
|---|---|
| AAAA | — |
| NS | a.dnspod.com, b.dnspod.com, c.dnspod.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 162.209.201.221 answers for xbiquge.cc at resolver 1.1.1.1:53.
Hosting and geo
xbiquge.cc is placed in Los Angeles (Downtown Los Angeles), United States by the local geolocation database (db-ip).
| Address | 162.209.201.221 |
|---|---|
| Country | United States |
| City | Los Angeles (Downtown Los Angeles) |
| Source | db-ip |
SSL/TLS
The certificate for xbiquge.cc is valid, with 41 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | xbiquge.cc |
| Valid from | 13 September 2026 |
| Valid until | 12 December 2026 |
| Days left | 41 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: www.xbiquge.cc, xbiquge.cc.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://www.xbiquge.cc/": context deadline exceeded
Security
Family DNS for xbiquge.cc is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: tls issuer changed from empty to YE2.
- October 2026: tls not_after changed from empty to 2026-12-12T06:40:16Z.
- October 2026: tls protocol changed from empty to TLS 1.3.
- October 2026: tls valid changed from false to true.
- October 2026: geo city changed from empty to Los Angeles (Downtown Los Angeles).
- October 2026: geo country changed from empty to United States.
Questions
Is xbiquge.cc safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts xbiquge.cc?
xbiquge.cc is placed in Los Angeles (Downtown Los Angeles), United States.
When does xbiquge.cc expire?
xbiquge.cc expires on 16 December 2026 according to https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc.
Who owns xbiquge.cc?
The registry did not return a person or a company for xbiquge.cc. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/xbiquge.cc at 2026-10-30T13:36:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:36:10Z
- TLS source tls:443 at 2026-10-30T13:36:10Z
- HTTP source https://xbiquge.cc/ at 2026-10-30T13:36:10Z
- Tech source not available at 2026-10-30T13:36:10Z
- Geo source db-ip at 2026-10-30T13:36:10Z
- Safety source family DNS and local lists at 2026-10-30T13:36:10Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.