sbf.net.nz
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
sbf.net.nz was registered on 19 Oct 2017 via Key-Systems GmbH. WHOIS data came from a WHOIS query because RDAP is not published for this TLD.
sbf.net.nz publishes 2 nameservers. DNSSEC is not signed.
sbf.net.nz has 3 IPv4 addresses (104.26.4.236, 104.26.5.236, 172.67.74.103) and 3 IPv6 addresses (2606:4700:20::681a:4ec, 2606:4700:20::681a:5ec, 2606:4700:20::ac43:4a67). The geolocation database places 104.26.4.236 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 78 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, Google Hosted Libraries, PHP, Statcounter, YUI, jQuery and vBulletin. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for sbf.net.nz in the checks that ran.
sbf.net.nz was registered on 19 Oct 2017 via Key-Systems GmbH. The registry returned 2 status values and 2 nameservers from whois://whois.irs.net.nz.
| Registered | since 19 Oct 2017 |
|---|---|
| Created | 19 October 2017 |
| Updated | 23 October 2026 |
| Expires | — |
| Registrar | Key-Systems GmbH |
| Status | ok, autorenewperiod |
| Nameservers | mary.ns.cloudflare.com, pete.ns.cloudflare.com |
| DNSSEC | unknown |
| Source | whois://whois.irs.net.nz |
RDAP is not available for .net.nz
sbf.net.nz carries the status "ok". The status ok means no other EPP status is set. It is not a safety verdict.
Nameserver mary.ns.cloudflare.com is published for sbf.net.nz in the registration record from whois://whois.irs.net.nz.
Nameserver pete.ns.cloudflare.com is published for sbf.net.nz in the registration record from whois://whois.irs.net.nz.
sbf.net.nz has 6 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.4.236, 104.26.5.236, 172.67.74.103 |
|---|---|
| AAAA | 2606:4700:20::681a:4ec, 2606:4700:20::681a:5ec, 2606:4700:20::ac43:4a67 |
| NS | mary.ns.cloudflare.com, pete.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.26.4.236 answers for sbf.net.nz at resolver 1.1.1.1:53.
IPv4 address 104.26.5.236 answers for sbf.net.nz at resolver 1.1.1.1:53.
IPv4 address 172.67.74.103 answers for sbf.net.nz at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:4ec answers for sbf.net.nz at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:5ec answers for sbf.net.nz at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4a67 answers for sbf.net.nz at resolver 1.1.1.1:53.
sbf.net.nz is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.4.236 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for sbf.net.nz is valid, with 78 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | sbf.net.nz |
| Valid from | 19 October 2026 |
| Valid until | 17 January 2027 |
| Days left | 78 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.sbf.net.nz, sbf.net.nz.
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Hosted Libraries is filed under CDN.
PHP is filed under Programming languages.
Statcounter is filed under Analytics.
YUI is filed under JavaScript libraries.
jQuery is filed under JavaScript libraries.
vBulletin is filed under Message boards.
The homepage returned HTTP 200 in 177 ms. The target title is 30 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 177 ms |
| Title length | 30 yes |
| Quoted title | "The Asian Commercial Sex Scene" |
| Meta description | "Talk about commercial sex, prostitution in Singapore and Asia" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://sbfonline.site/ |
| Language | en |
| Links | 149 |
| Images | 91 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for sbf.net.nz 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 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 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
sbf.net.nz is placed in Toronto, Canada.
No expiry date was returned for sbf.net.nz.
The registry did not return a person or a company for sbf.net.nz. RDAP often redacts the registrant. The registrar on file is Key-Systems GmbH.
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.