bouncyballs.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
bouncyballs.org was registered on 6 Dec 2013 via Tucows Domains Inc. and the registry expiry is 6 Dec 2026. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org.
bouncyballs.org publishes 2 nameservers. DNSSEC is not signed.
bouncyballs.org has 2 IPv4 addresses (104.21.78.215, 172.67.137.162) and 2 IPv6 addresses (2606:4700:3033::6815:4ed7, 2606:4700:3033::ac43:89a2). The geolocation database places 104.21.78.215 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for bouncyballs.org in the checks that ran.
bouncyballs.org was registered on 6 Dec 2013 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org.
| Registered | since 6 Dec 2013 |
|---|---|
| Created | 6 December 2013 |
| Updated | 12 August 2026 |
| Expires | 6 December 2026 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | ian.ns.cloudflare.com, jean.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org |
bouncyballs.org 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.
bouncyballs.org 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 ian.ns.cloudflare.com is published for bouncyballs.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org.
Nameserver jean.ns.cloudflare.com is published for bouncyballs.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org.
bouncyballs.org has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.78.215, 172.67.137.162 |
|---|---|
| AAAA | 2606:4700:3033::6815:4ed7, 2606:4700:3033::ac43:89a2 |
| NS | ian.ns.cloudflare.com, jean.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.78.215 answers for bouncyballs.org at resolver 1.1.1.1:53.
IPv4 address 172.67.137.162 answers for bouncyballs.org at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::6815:4ed7 answers for bouncyballs.org at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:89a2 answers for bouncyballs.org at resolver 1.1.1.1:53.
bouncyballs.org is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.78.215 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for bouncyballs.org is valid, with 62 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bouncyballs.org |
| Valid from | 3 October 2026 |
| Valid until | 1 January 2027 |
| Days left | 62 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bouncyballs.org, bouncyballs.org.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 140 ms. The target title is 58 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 140 ms |
| Title length | 58 yes |
| Quoted title | "Bouncy Balls – Manage classroom noise with bouncing balls!" |
| Meta description | "A free classroom noise level meter, monitor and management tool. Perfect if your school kids are too noisy! Bouncing balls react to sounds from the microphone." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 3 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for bouncyballs.org 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 | yes |
| 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 5 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.
bouncyballs.org is placed in Toronto, Canada.
bouncyballs.org expires on 6 December 2026 according to https://rdap.publicinterestregistry.org/rdap/domain/bouncyballs.org.
The registry did not return a person or a company for bouncyballs.org. 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.