zoobeeg.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
zoobeeg.net was registered on 31 May 2020 via Tucows Domains Inc. and the registry expiry is 31 May 2028. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/zoobeeg.net.
zoobeeg.net publishes 2 nameservers. DNSSEC is not signed.
zoobeeg.net has 2 IPv4 addresses (104.21.7.110, 172.67.130.34) and 2 IPv6 addresses (2606:4700:3031::6815:76e, 2606:4700:3035::ac43:8222). The geolocation database places 104.21.7.110 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS, HTTP/3, jQuery, jQuery CDN and jQuery UI. The fingerprints ran on the homepage that was already downloaded.
zoobeeg.net was registered on 31 May 2020 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/zoobeeg.net.
| Registered | since 31 May 2020 |
|---|---|
| Created | 31 May 2020 |
| Updated | 23 June 2026 |
| Expires | 31 May 2028 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | chad.ns.cloudflare.com, isla.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/zoobeeg.net |
zoobeeg.net 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.
zoobeeg.net 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 chad.ns.cloudflare.com is published for zoobeeg.net in the registration record from https://rdap.verisign.com/net/v1/domain/zoobeeg.net.
Nameserver isla.ns.cloudflare.com is published for zoobeeg.net in the registration record from https://rdap.verisign.com/net/v1/domain/zoobeeg.net.
zoobeeg.net has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.7.110, 172.67.130.34 |
|---|---|
| AAAA | 2606:4700:3031::6815:76e, 2606:4700:3035::ac43:8222 |
| NS | chad.ns.cloudflare.com, isla.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.7.110 answers for zoobeeg.net at resolver 1.1.1.1:53.
IPv4 address 172.67.130.34 answers for zoobeeg.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::6815:76e answers for zoobeeg.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:8222 answers for zoobeeg.net at resolver 1.1.1.1:53.
zoobeeg.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.7.110 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for zoobeeg.net is valid, with 88 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | zoobeeg.net |
| Valid from | 29 October 2026 |
| Valid until | 27 January 2027 |
| Days left | 88 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.zoobeeg.net, zoobeeg.net.
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
jQuery UI is filed under JavaScript libraries.
The homepage returned HTTP 200 in 97 ms. The target title is 11 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 97 ms |
| Title length | 11 yes |
| Quoted title | "zoobeeg.net" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 545 |
| Images | 163 |
| 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 zoobeeg.net 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 | yes |
| CSP | no |
Cloudflare family DNS returned a block for zoobeeg.net. 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 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 5 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 zoobeeg.net. That resolver covers adult and malware names.
zoobeeg.net is placed in Toronto, Canada.
zoobeeg.net expires on 31 May 2028 according to https://rdap.verisign.com/net/v1/domain/zoobeeg.net.
The registry did not return a person or a company for zoobeeg.net. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
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.