whalesmining.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 58 days left4 years old
30
whalesmining.com was registered on 26 Dec 2021 via eNom, LLC and the registry expiry is 26 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/whalesmining.com.
whalesmining.com publishes 5 nameservers. DNSSEC is not signed.
whalesmining.com has 1 IPv4 address (155.138.228.232). The geolocation database places 155.138.228.232 in Atlanta, United States.
The TLS certificate from YE2 is not valid (TLS 1.3).
No safety warning was recorded for whalesmining.com in the checks that ran.
Domain · RDAP/WHOIS
whalesmining.com was registered on 26 Dec 2021 via eNom, LLC. The registry returned 1 status value and 5 nameservers from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
| Registered | since 26 Dec 2021 |
|---|---|
| Created | 26 December 2021 |
| Updated | 4 January 2025 |
| Expires | 26 December 2026 |
| Registrar | eNom, LLC |
| Status | active |
| Nameservers | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/whalesmining.com |
Nameserver dns1.name-services.com is published for whalesmining.com in the registration record from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
Nameserver dns2.name-services.com is published for whalesmining.com in the registration record from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
Nameserver dns3.name-services.com is published for whalesmining.com in the registration record from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
Nameserver dns4.name-services.com is published for whalesmining.com in the registration record from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
Nameserver dns5.name-services.com is published for whalesmining.com in the registration record from https://rdap.verisign.com/com/v1/domain/whalesmining.com.
DNS
whalesmining.com has 1 address record, 0 mail exchangers and 5 nameservers, measured at 1.1.1.1:53.
| A | 155.138.228.232 |
|---|---|
| AAAA | — |
| NS | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 155.138.228.232 answers for whalesmining.com at resolver 1.1.1.1:53.
A random label under whalesmining.com also resolved, which means wildcard DNS is on.
Hosting and geo
whalesmining.com is placed in Atlanta, United States by the local geolocation database (db-ip).
| Address | 155.138.228.232 |
|---|---|
| Country | United States |
| City | Atlanta |
| Source | db-ip |
SSL/TLS
The certificate for whalesmining.com is not valid, with 58 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | access.chilam.app |
| Valid from | 30 September 2026 |
| Valid until | 29 December 2026 |
| Days left | 58 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: access.chilam.app.
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://whalesmining.com/": tls: failed to verify certificate: x509: certificate is valid for access.chilam.app, not whalesmining.com
Security
Family DNS for whalesmining.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 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.
Change history
- October 2026: geo city changed from empty to Atlanta.
- October 2026: geo country changed from empty to United States.
Questions
Is whalesmining.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 whalesmining.com?
whalesmining.com is placed in Atlanta, United States.
When does whalesmining.com expire?
whalesmining.com expires on 26 December 2026 according to https://rdap.verisign.com/com/v1/domain/whalesmining.com.
Who owns whalesmining.com?
The registry did not return a person or a company for whalesmining.com. RDAP often redacts the registrant. The registrar on file is eNom, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/whalesmining.com at 2026-10-30T14:19:58Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:19:58Z
- TLS source tls:443 at 2026-10-30T14:19:58Z
- HTTP source https://whalesmining.com/ at 2026-10-30T14:19:58Z
- Tech source not available at 2026-10-30T14:19:58Z
- Geo source db-ip at 2026-10-30T14:19:58Z
- Safety source family DNS and local lists at 2026-10-30T14:19:58Z
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.