streamlord.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked12 years old
20
streamlord.com was registered on 4 Aug 2014 via Gransy, s.r.o. and the registry expiry is 4 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/streamlord.com.
streamlord.com publishes 5 nameservers. DNSSEC is not signed.
streamlord.com has 1 IPv4 address (104.244.73.87). The geolocation database places 104.244.73.87 in Bissen, Luxembourg.
Domain · RDAP/WHOIS
streamlord.com was registered on 4 Aug 2014 via Gransy, s.r.o.. The registry returned 1 status value and 5 nameservers from https://rdap.verisign.com/com/v1/domain/streamlord.com.
| Registered | since 4 Aug 2014 |
|---|---|
| Created | 4 August 2014 |
| Updated | 8 August 2026 |
| Expires | 4 August 2027 |
| Registrar | Gransy, s.r.o. |
| Status | client transfer prohibited |
| Nameservers | ns.gransy.com, ns2.gransy.com, ns3.gransy.com, ns4.gransy.com, ns5.gransy.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/streamlord.com |
streamlord.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 ns.gransy.com is published for streamlord.com in the registration record from https://rdap.verisign.com/com/v1/domain/streamlord.com.
Nameserver ns2.gransy.com is published for streamlord.com in the registration record from https://rdap.verisign.com/com/v1/domain/streamlord.com.
Nameserver ns3.gransy.com is published for streamlord.com in the registration record from https://rdap.verisign.com/com/v1/domain/streamlord.com.
Nameserver ns4.gransy.com is published for streamlord.com in the registration record from https://rdap.verisign.com/com/v1/domain/streamlord.com.
Nameserver ns5.gransy.com is published for streamlord.com in the registration record from https://rdap.verisign.com/com/v1/domain/streamlord.com.
DNS
streamlord.com has 1 address record, 2 mail exchangers and 5 nameservers, measured at 1.1.1.1:53.
| A | 104.244.73.87 |
|---|---|
| AAAA | — |
| NS | ns.gransy.com, ns2.gransy.com, ns3.gransy.com, ns4.gransy.com, ns5.gransy.com |
| MX | mx.zoho.com (10) Zoho, mx2.zoho.com (20) Zoho |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at streamlord.com is "v=spf1 include:zoho.com ~all".
IPv4 address 104.244.73.87 answers for streamlord.com at resolver 1.1.1.1:53.
Mail exchanger mx.zoho.com has preference 10. The host is recognised as Zoho.
Mail exchanger mx2.zoho.com has preference 20. The host is recognised as Zoho.
A random label under streamlord.com also resolved, which means wildcard DNS is on.
Hosting and geo
streamlord.com is placed in Bissen, Luxembourg by the local geolocation database (db-ip).
| Address | 104.244.73.87 |
|---|---|
| Country | Luxembourg |
| City | Bissen |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for streamlord.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 104.244.73.87:443: connect: connection refused
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://streamlord.com/": dial tcp 104.244.73.87:443: connect: connection refused
Security
Family DNS for streamlord.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 streamlord.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 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 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 Bissen.
- October 2026: geo country changed from empty to Luxembourg.
Questions
Is streamlord.com safe?
Cloudflare family DNS returned a block for streamlord.com. That resolver covers adult and malware names.
Who hosts streamlord.com?
streamlord.com is placed in Bissen, Luxembourg.
When does streamlord.com expire?
streamlord.com expires on 4 August 2027 according to https://rdap.verisign.com/com/v1/domain/streamlord.com.
Who owns streamlord.com?
The registry did not return a person or a company for streamlord.com. RDAP often redacts the registrant. The registrar on file is Gransy, s.r.o..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/streamlord.com at 2026-10-30T14:15:08Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:15:08Z
- TLS source tls:443 at 2026-10-30T14:15:08Z
- HTTP source https://streamlord.com/ at 2026-10-30T14:15:08Z
- Tech source not available at 2026-10-30T14:15:08Z
- Geo source db-ip at 2026-10-30T14:15:08Z
- Safety source family DNS and local lists at 2026-10-30T14:15:08Z
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.