bbbjk5.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
32
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
32
bbbjk5.com was registered on 18 Mar 2026 via SNAPNAMES 31, LLC and the registry expiry is 18 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/bbbjk5.com.
bbbjk5.com publishes 2 nameservers. DNSSEC is not signed.
bbbjk5.com has 4 IPv4 addresses (110.242.74.102, 111.63.65.103, 111.63.65.247, 124.237.177.164). The geolocation database places 110.242.74.102 in Chengde, China.
The TLS certificate from GlobalSign RSA OV SSL CA 2018 is not valid (TLS 1.2).
No safety warning was recorded for bbbjk5.com in the checks that ran.
bbbjk5.com was registered on 18 Mar 2026 via SNAPNAMES 31, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/bbbjk5.com.
| Registered | since 18 Mar 2026 |
|---|---|
| Created | 18 March 2026 |
| Updated | 28 August 2026 |
| Expires | 18 March 2027 |
| Registrar | SNAPNAMES 31, LLC |
| Status | active |
| Nameservers | a11.share-dns.com, b11.share-dns.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/bbbjk5.com |
Nameserver a11.share-dns.com is published for bbbjk5.com in the registration record from https://rdap.verisign.com/com/v1/domain/bbbjk5.com.
Nameserver b11.share-dns.net is published for bbbjk5.com in the registration record from https://rdap.verisign.com/com/v1/domain/bbbjk5.com.
bbbjk5.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 110.242.74.102, 111.63.65.103, 111.63.65.247, 124.237.177.164 |
|---|---|
| AAAA | — |
| NS | a.share-dns.com, b.share-dns.net |
| MX | mx.maillb.baidu.com (10), mx.baidu.com (20) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at bbbjk5.com is "v=spf1 include:spf1.baidu.com include:spf2.baidu.com include:spf3.baidu.com include:spf4.baidu.com -all".
IPv4 address 110.242.74.102 answers for bbbjk5.com at resolver 1.1.1.1:53.
IPv4 address 111.63.65.103 answers for bbbjk5.com at resolver 1.1.1.1:53.
IPv4 address 111.63.65.247 answers for bbbjk5.com at resolver 1.1.1.1:53.
IPv4 address 124.237.177.164 answers for bbbjk5.com at resolver 1.1.1.1:53.
Mail exchanger mx.maillb.baidu.com has preference 10.
Mail exchanger mx.baidu.com has preference 20.
A random label under bbbjk5.com also resolved, which means wildcard DNS is on.
bbbjk5.com is placed in Chengde, China by the local geolocation database (db-ip).
| Address | 110.242.74.102 |
|---|---|
| Country | China |
| City | Chengde |
| Source | db-ip |
The certificate for bbbjk5.com is not valid, with 84 days left and 53 subject alternative names. Source: tls:443.
| Issuer | GlobalSign RSA OV SSL CA 2018 |
|---|---|
| Subject | baidu.com |
| Valid from | 9 July 2026 |
| Valid until | 24 January 2027 |
| Days left | 84 |
| SAN count | 53 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.91.com, *.aipage.cn, *.aipage.com, *.apollo.auto, *.baidu.com, *.baidubce.com, *.baiducontent.com, *.baidupcs.com, *.baidustatic.com, *.baifubao.com, *.bce.baidu.com, *.bcehost.com, *.bdimg.com, *.bdstatic.com, *.bdtjrcv.com, *.bj.baidubce.com, *.chuanke.com, *.cloud.baidu.com, *.dlnel.com, *.dlnel.org, *.dueros.baidu.com, *.eyun.baidu.com, *.fanyi.baidu.com, *.gz.baidubce.com, *.hao123.baidu.com, *.hao123.com, *.hao222.com, *.haokan.com, *.im.baidu.com, *.map.baidu.com, *.mbd.baidu.com, *.mipcdn.com, *.news.baidu.com, *.nuomi.com, *.pae.baidu.com, *.safe.baidu.com, *.smartapps.cn, *.su.baidu.com, *.trustgo.com, *.vd.bdstatic.com, *.xueshu.baidu.com, apollo.auto, baidu.com, baifubao.com, click.hm.baidu.com, cm.pos.baidu.com, dwz.cn, log.hm.baidu.com, mct.y.nuomi.com, update.pan.baidu.com, wn.pos.baidu.com, www.baidu.cn, www.baidu.com.cn.
Validation result: certificate did not validate
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://bbbjk5.com/": tls: failed to verify certificate: x509: certificate is valid for baidu.com, click.hm.baidu.com, baifubao.com, www.baidu.cn, www.baidu.com.cn, mct.y.nuomi.com, apollo.auto, dwz.cn, update.pan.baidu.com, wn.pos.bai
Family DNS for bbbjk5.com 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.
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 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 2 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
bbbjk5.com is placed in Chengde, China.
bbbjk5.com expires on 18 March 2027 according to https://rdap.verisign.com/com/v1/domain/bbbjk5.com.
The registry did not return a person or a company for bbbjk5.com. RDAP often redacts the registrant. The registrar on file is SNAPNAMES 31, LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.