24baze.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 65 days leftUnder 1 year old
32
24baze.com was registered on 15 Nov 2025 via Spaceship, Inc. and the registry expiry is 15 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/24baze.com.
24baze.com publishes 4 nameservers. DNSSEC is not signed.
24baze.com has 1 IPv4 address (185.151.30.142) and 1 IPv6 address (2a07:7800::142). The geolocation database places 185.151.30.142 in London, United Kingdom.
The TLS certificate from RapidSSL TLS RSA CA G1 is not valid (TLS 1.3).
No safety warning was recorded for 24baze.com in the checks that ran.
Domain · RDAP/WHOIS
24baze.com was registered on 15 Nov 2025 via Spaceship, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/24baze.com.
| Registered | since 15 Nov 2025 |
|---|---|
| Created | 15 November 2025 |
| Updated | 16 November 2025 |
| Expires | 15 November 2026 |
| Registrar | Spaceship, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.stackdns.com, ns2.stackdns.com, ns3.stackdns.com, ns4.stackdns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/24baze.com |
24baze.com 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.
Nameserver ns1.stackdns.com is published for 24baze.com in the registration record from https://rdap.verisign.com/com/v1/domain/24baze.com.
Nameserver ns2.stackdns.com is published for 24baze.com in the registration record from https://rdap.verisign.com/com/v1/domain/24baze.com.
Nameserver ns3.stackdns.com is published for 24baze.com in the registration record from https://rdap.verisign.com/com/v1/domain/24baze.com.
Nameserver ns4.stackdns.com is published for 24baze.com in the registration record from https://rdap.verisign.com/com/v1/domain/24baze.com.
DNS
24baze.com has 2 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 185.151.30.142 |
|---|---|
| AAAA | 2a07:7800::142 |
| NS | ns1.stackdns.com, ns2.stackdns.com, ns3.stackdns.com, ns4.stackdns.com |
| MX | mx.stackmail.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at 24baze.com is "v=spf1 include:spf.stackmail.com a mx -all".
IPv4 address 185.151.30.142 answers for 24baze.com at resolver 1.1.1.1:53.
IPv6 address 2a07:7800::142 answers for 24baze.com at resolver 1.1.1.1:53.
Mail exchanger mx.stackmail.com has preference 10.
A random label under 24baze.com also resolved, which means wildcard DNS is on.
Hosting and geo
24baze.com is placed in London, United Kingdom by the local geolocation database (db-ip).
| Address | 185.151.30.142 |
|---|---|
| Country | United Kingdom |
| City | London |
| Source | db-ip |
SSL/TLS
The certificate for 24baze.com is not valid, with 65 days left and 2 subject alternative names. Source: tls:443.
| Issuer | RapidSSL TLS RSA CA G1 |
|---|---|
| Subject | *.stackcp.com |
| Valid from | 20 June 2026 |
| Valid until | 4 January 2027 |
| Days left | 65 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.stackcp.com, stackcp.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://24baze.com/": tls: failed to verify certificate: x509: certificate is valid for *.stackcp.com, stackcp.com, not 24baze.com
Security
Family DNS for 24baze.com 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.
Score breakdown
Availability 10 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 5 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 2 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to London.
- October 2026: geo country changed from empty to United Kingdom.
Questions
Is 24baze.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts 24baze.com?
24baze.com is placed in London, United Kingdom.
When does 24baze.com expire?
24baze.com expires on 15 November 2026 according to https://rdap.verisign.com/com/v1/domain/24baze.com.
Who owns 24baze.com?
The registry did not return a person or a company for 24baze.com. RDAP often redacts the registrant. The registrar on file is Spaceship, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/24baze.com at 2026-10-30T13:41:12Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:41:12Z
- TLS source tls:443 at 2026-10-30T13:41:12Z
- HTTP source https://24baze.com/ at 2026-10-30T13:41:12Z
- Tech source not available at 2026-10-30T13:41:12Z
- Geo source db-ip at 2026-10-30T13:41:12Z
- Safety source family DNS and local lists at 2026-10-30T13:41:12Z
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.