b9good.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
5
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
5
b9good.com was registered on 15 Jan 2017 via GoDaddy.com, LLC and the registry expiry is 15 Jan 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/b9good.com.
b9good.com was registered on 15 Jan 2017 via GoDaddy.com, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/b9good.com.
| Registered | since 15 Jan 2017 |
|---|---|
| Created | 15 January 2017 |
| Updated | 21 February 2024 |
| Expires | 15 January 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | active |
| Nameservers | vip3.alidns.com, vip4.alidns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/b9good.com |
Nameserver vip3.alidns.com is published for b9good.com in the registration record from https://rdap.verisign.com/com/v1/domain/b9good.com.
Nameserver vip4.alidns.com is published for b9good.com in the registration record from https://rdap.verisign.com/com/v1/domain/b9good.com.
b9good.com has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
read udp 10.0.0.3:51458->8.8.8.8:53: i/o timeout
Geolocation for b9good.com is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
No TLS certificate was read for b9good.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup b9good.com: i/o timeout
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://b9good.com/": dial tcp: lookup b9good.com on 46.38.225.230:53: server misbehaving
Family DNS for b9good.com is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for b9good.com. That resolver covers adult and malware names.
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 0 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 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 0 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for b9good.com. That resolver covers adult and malware names.
The host network is not available without a local geolocation database.
b9good.com expires on 15 January 2028 according to https://rdap.verisign.com/com/v1/domain/b9good.com.
The registry did not return a person or a company for b9good.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, 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.