hornresp.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
35
hornresp.net was registered on 9 Apr 2013 via Mesh Digital Limited and the registry expiry is 9 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/hornresp.net.
hornresp.net publishes 2 nameservers. DNSSEC is not signed.
hornresp.net has 1 IPv4 address (80.237.132.235) and 1 IPv6 address (2a01:488:42:1000:50ed:84eb:ff60:998e). The geolocation database places 80.237.132.235 in Cologne, Germany.
No safety warning was recorded for hornresp.net in the checks that ran.
hornresp.net was registered on 9 Apr 2013 via Mesh Digital Limited. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/hornresp.net.
| Registered | since 9 Apr 2013 |
|---|---|
| Created | 9 April 2013 |
| Updated | 10 March 2026 |
| Expires | 9 April 2027 |
| Registrar | Mesh Digital Limited |
| Status | active |
| Nameservers | ns35.domaincontrol.com, ns36.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/hornresp.net |
Nameserver ns35.domaincontrol.com is published for hornresp.net in the registration record from https://rdap.verisign.com/net/v1/domain/hornresp.net.
Nameserver ns36.domaincontrol.com is published for hornresp.net in the registration record from https://rdap.verisign.com/net/v1/domain/hornresp.net.
hornresp.net has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 80.237.132.235 |
|---|---|
| AAAA | 2a01:488:42:1000:50ed:84eb:ff60:998e |
| NS | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | mx0.hornresp.net (50) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hornresp.net is "v=spf1 a mx include:spf.server-he.de -all".
IPv4 address 80.237.132.235 answers for hornresp.net at resolver 1.1.1.1:53.
IPv6 address 2a01:488:42:1000:50ed:84eb:ff60:998e answers for hornresp.net at resolver 1.1.1.1:53.
Mail exchanger mx0.hornresp.net has preference 50.
hornresp.net is placed in Cologne, Germany by the local geolocation database (db-ip).
| Address | 80.237.132.235 |
|---|---|
| Country | Germany |
| City | Cologne |
| Source | db-ip |
No TLS certificate was read for hornresp.net on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 80.237.132.235:443: connect: connection refused
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://hornresp.net/": dial tcp 80.237.132.235:443: connect: connection refused
Family DNS for hornresp.net 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.
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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
hornresp.net is placed in Cologne, Germany.
hornresp.net expires on 9 April 2027 according to https://rdap.verisign.com/net/v1/domain/hornresp.net.
The registry did not return a person or a company for hornresp.net. RDAP often redacts the registrant. The registrar on file is Mesh Digital Limited.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.