statsmash.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe7 years old
35
statsmash.com was registered on 26 Apr 2019 via Name.com, Inc. and the registry expiry is 26 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/statsmash.com.
statsmash.com publishes 4 nameservers. DNSSEC is not signed.
statsmash.com has 1 IPv4 address (142.11.196.199). The geolocation database places 142.11.196.199 in Dallas, United States.
No safety warning was recorded for statsmash.com in the checks that ran.
Domain · RDAP/WHOIS
statsmash.com was registered on 26 Apr 2019 via Name.com, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/statsmash.com.
| Registered | since 26 Apr 2019 |
|---|---|
| Created | 26 April 2019 |
| Updated | 4 April 2026 |
| Expires | 26 April 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | caiman.ezoicns.com, ferret.ezoicns.com, jackal.ezoicns.com, walrus.ezoicns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/statsmash.com |
statsmash.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 caiman.ezoicns.com is published for statsmash.com in the registration record from https://rdap.verisign.com/com/v1/domain/statsmash.com.
Nameserver ferret.ezoicns.com is published for statsmash.com in the registration record from https://rdap.verisign.com/com/v1/domain/statsmash.com.
Nameserver jackal.ezoicns.com is published for statsmash.com in the registration record from https://rdap.verisign.com/com/v1/domain/statsmash.com.
Nameserver walrus.ezoicns.com is published for statsmash.com in the registration record from https://rdap.verisign.com/com/v1/domain/statsmash.com.
DNS
statsmash.com has 1 address record, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 142.11.196.199 |
|---|---|
| AAAA | — |
| NS | caiman.ezoicns.com, ferret.ezoicns.com, jackal.ezoicns.com, walrus.ezoicns.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, aspmx2.googlemail.com (10) Google, aspmx3.googlemail.com (10) Google |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at statsmash.com is "v=spf1 include:_spf.google.com ~all".
IPv4 address 142.11.196.199 answers for statsmash.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 10. The host is recognised as Google.
Hosting and geo
statsmash.com is placed in Dallas, United States by the local geolocation database (db-ip).
| Address | 142.11.196.199 |
|---|---|
| Country | United States |
| City | Dallas |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for statsmash.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 142.11.196.199:443: i/o timeout
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 |
|---|
context deadline exceeded
Security
Family DNS for statsmash.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 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Dallas.
- October 2026: geo country changed from empty to United States.
Questions
Is statsmash.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 statsmash.com?
statsmash.com is placed in Dallas, United States.
When does statsmash.com expire?
statsmash.com expires on 26 April 2027 according to https://rdap.verisign.com/com/v1/domain/statsmash.com.
Who owns statsmash.com?
The registry did not return a person or a company for statsmash.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/statsmash.com at 2026-10-30T14:15:11Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:15:11Z
- TLS source tls:443 at 2026-10-30T14:15:11Z
- HTTP source https://statsmash.com/ at 2026-10-30T14:15:11Z
- Tech source not available at 2026-10-30T14:15:11Z
- Geo source db-ip at 2026-10-30T14:15:11Z
- Safety source family DNS and local lists at 2026-10-30T14:15:11Z
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.