bbw-chan.nl
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 55 days left2 years old
50
bbw-chan.nl was registered on 26 Dec 2023 via Registrar.eu. WHOIS data came from RDAP at https://rdap.sidn.nl/domain/bbw-chan.nl.
bbw-chan.nl publishes 2 nameservers. DNSSEC is not signed.
bbw-chan.nl has 2 IPv4 addresses (104.21.4.110, 172.67.132.3) and 2 IPv6 addresses (2606:4700:3033::6815:46e, 2606:4700:3035::ac43:8403). The geolocation database places 104.21.4.110 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Bot Management and Envoy. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
bbw-chan.nl was registered on 26 Dec 2023 via Registrar.eu. The registry returned 1 status value and 2 nameservers from https://rdap.sidn.nl/domain/bbw-chan.nl.
| Registered | since 26 Dec 2023 |
|---|---|
| Created | 26 December 2023 |
| Updated | 11 July 2025 |
| Expires | — |
| Registrar | Registrar.eu |
| Status | active |
| Nameservers | lewis.ns.cloudflare.com, princess.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.sidn.nl/domain/bbw-chan.nl |
Nameserver lewis.ns.cloudflare.com is published for bbw-chan.nl in the registration record from https://rdap.sidn.nl/domain/bbw-chan.nl.
Nameserver princess.ns.cloudflare.com is published for bbw-chan.nl in the registration record from https://rdap.sidn.nl/domain/bbw-chan.nl.
DNS
bbw-chan.nl has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.4.110, 172.67.132.3 |
|---|---|
| AAAA | 2606:4700:3033::6815:46e, 2606:4700:3035::ac43:8403 |
| NS | lewis.ns.cloudflare.com, princess.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.4.110 answers for bbw-chan.nl at resolver 1.1.1.1:53.
IPv4 address 172.67.132.3 answers for bbw-chan.nl at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::6815:46e answers for bbw-chan.nl at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:8403 answers for bbw-chan.nl at resolver 1.1.1.1:53.
A random label under bbw-chan.nl also resolved, which means wildcard DNS is on.
Hosting and geo
bbw-chan.nl is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.4.110 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for bbw-chan.nl is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bbw-chan.nl |
| Valid from | 27 September 2026 |
| Valid until | 26 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bbw-chan.nl, bbw-chan.nl.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- Envoy · Reverse proxies
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
Envoy is filed under Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 18 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 18 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for bbw-chan.nl 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 bbw-chan.nl. 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.
Score breakdown
Availability 25 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 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is bbw-chan.nl safe?
Cloudflare family DNS returned a block for bbw-chan.nl. That resolver covers adult and malware names.
Who hosts bbw-chan.nl?
bbw-chan.nl is placed in Toronto, Canada.
When does bbw-chan.nl expire?
No expiry date was returned for bbw-chan.nl.
Who owns bbw-chan.nl?
The registry did not return a person or a company for bbw-chan.nl. RDAP often redacts the registrant. The registrar on file is Registrar.eu.
Sources
- RDAP source https://rdap.sidn.nl/domain/bbw-chan.nl at 2026-10-30T14:59:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:59:10Z
- TLS source tls:443 at 2026-10-30T14:59:10Z
- HTTP source https://bbw-chan.nl/ at 2026-10-30T14:59:10Z
- Tech source wappalyzergo at 2026-10-30T14:59:10Z
- Geo source db-ip at 2026-10-30T14:59:10Z
- Safety source family DNS and local lists at 2026-10-30T14:59: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.