smashystream.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 82 days left4 years oldTranco #730826
15
smashystream.com was registered on 31 Dec 2021 via NameSilo, LLC and the registry expiry is 31 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/smashystream.com.
smashystream.com publishes 3 nameservers. DNSSEC is not signed.
smashystream.com has 1 IPv4 address (209.112.89.55). The geolocation database places 209.112.89.55 in Frankfurt am Main (Innenstadt I), Germany.
The TLS certificate from YR1 is not valid (TLS 1.3).
Domain · RDAP/WHOIS
smashystream.com was registered on 31 Dec 2021 via NameSilo, LLC. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/smashystream.com.
| Registered | since 31 Dec 2021 |
|---|---|
| Created | 31 December 2021 |
| Updated | 17 April 2026 |
| Expires | 31 December 2026 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/smashystream.com |
smashystream.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.dnsowl.com is published for smashystream.com in the registration record from https://rdap.verisign.com/com/v1/domain/smashystream.com.
Nameserver ns2.dnsowl.com is published for smashystream.com in the registration record from https://rdap.verisign.com/com/v1/domain/smashystream.com.
Nameserver ns3.dnsowl.com is published for smashystream.com in the registration record from https://rdap.verisign.com/com/v1/domain/smashystream.com.
DNS
smashystream.com has 1 address record, 0 mail exchangers and 3 nameservers, measured at 1.1.1.1:53.
| A | 209.112.89.55 |
|---|---|
| AAAA | — |
| NS | ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 209.112.89.55 answers for smashystream.com at resolver 1.1.1.1:53.
Hosting and geo
smashystream.com is placed in Frankfurt am Main (Innenstadt I), Germany by the local geolocation database (db-ip).
| Address | 209.112.89.55 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main (Innenstadt I) |
| Source | db-ip |
SSL/TLS
The certificate for smashystream.com is not valid, with 82 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR1 |
|---|---|
| Subject | tools.anyembed.xyz |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 82 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: tools.anyembed.xyz.
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://smashystream.com/": tls: failed to verify certificate: x509: certificate is valid for tools.anyembed.xyz, not smashystream.com
Security
Family DNS for smashystream.com 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 | no |
| CSP | no |
Cloudflare family DNS returned a block for smashystream.com. 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.
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 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.
Change history
- October 2026: geo city changed from empty to Frankfurt am Main (Innenstadt I).
- October 2026: geo country changed from empty to Germany.
Questions
Is smashystream.com safe?
Cloudflare family DNS returned a block for smashystream.com. That resolver covers adult and malware names.
Who hosts smashystream.com?
smashystream.com is placed in Frankfurt am Main (Innenstadt I), Germany.
When does smashystream.com expire?
smashystream.com expires on 31 December 2026 according to https://rdap.verisign.com/com/v1/domain/smashystream.com.
Who owns smashystream.com?
The registry did not return a person or a company for smashystream.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/smashystream.com at 2026-10-30T14:14:19Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:14:19Z
- TLS source tls:443 at 2026-10-30T14:14:19Z
- HTTP source https://smashystream.com/ at 2026-10-30T14:14:19Z
- Tech source not available at 2026-10-30T14:14:19Z
- Geo source db-ip at 2026-10-30T14:14:19Z
- Safety source family DNS and local lists at 2026-10-30T14:14:19Z
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.