🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`hypersecure.cloud`

DNSSEC	⚠️ Not signed
A	2001:8d8:100f:f000::200^{🇩🇪 IONOS-AS2001:8d8::/32 DE-IONOS-20020910}
		PTR	`2001-08d8-100f-f000-0000-0000-0000-0200.elastic-ssl.ui-r.com`
A	217.160.0.161^{🇩🇪 IONOS-AS217.160.0.0/16 IONOS-PA-3}
NS	`docks02.rzone.de` ⭐
		A	2001:8d8:fe:53:5747:2a74:d:2^{IONOS-AS2001:8d8:fe::/47 IONOS AS8560 anycast more specific}
		A	217.160.80.129^{IONOS-AS217.160.80.0/22 AS8560 anycast more specific}
NS	`shades17.rzone.de`
		A	2607:f1c0:fe:53:185:132:34:144^{🇺🇸 IONOS-ANYCAST2607:f1c0:fe::/47 AS8560 global anycast services (more specific) 1&1 IONOS Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
			PTR	`shades17.rzone.de`
		A	185.132.34.144^{🇩🇪 IONOS-ANYCAST185.132.32.0/22 IONOS DNSAS (eBGP DNS)}
			PTR	`shades17.rzone.de`
MX	`smtpin.rzone.de` ⭐
		A	2a01:238:20a:202:50f0::1097^{🇩🇪 STRATO2a01:238:20a::/48 Strato AG}
		A	81.169.145.97^{🇩🇪 STRATO81.169.144.0/22 AG}
			PTR	`smtpin.rzone.de`
SOA	`docks02.rzone.de`hostmaster@strato-rz.de 2023-10-26 #91

`cloud`

	DNSSEC	⚠️ Not signed
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1790862329

Same first word

hypersecure.com

hypersecure.in

hypersecure.net

hypersecure.jp

hypersecure.cloud

hypersecure.org

hypersecure.de

hypersecure.xyz

Similar names

securehyper.com

securehyper.com.au

hyperrescue.mobi

hyperrescue.com

rescuehyper.xyz

Previous names

Next names

DNS History

5 records (5 active, 0 former)

●NSdocks02.rzone.de2026-09-29 → 2026-10-01 · 2 obs

● 2026-09-29 09:07:12
● 2026-10-01 14:14:58

●NSshades17.rzone.de2026-09-29 → 2026-10-01 · 2 obs

● 2026-09-29 09:07:12
● 2026-10-01 14:14:58

●MXsmtpin.rzone.de2026-09-29 → 2026-10-01 · 2 obs

● 2026-09-29 09:07:12
● 2026-10-01 14:14:58

●A2001:8d8:100f:f000::2002026-09-29 → 2026-10-01 · 2 obs

● 2026-09-29 09:07:12
● 2026-10-01 14:14:58

●A217.160.0.1612026-09-29 → 2026-10-01 · 2 obs

● 2026-09-29 09:07:12
● 2026-10-01 14:14:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cloud	ns10.trs-dns.info, ns01.trs-dns.net, ns01.trs-dns.com, ns10.trs-dns.org	-
hypersecure.cloud	shades17.rzone.de, docks02.rzone.de	-

✅ Authoritative Response

Server:217.160.80.129

NS records: shades17.rzone.de, docks02.rzone.de

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hypersecure.cloud (unsigned zone)

⏱️ Timing

Total: 1244ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.160.0.161`
AAAA	1	`2001:8d8:100f:f000::200`
NS	2	`docks02.rzone.de, shades17.rzone.de`
MX	1	`smtpin.rzone.de (pri: 5)`
SOA	1	`docks02.rzone.de hostmaster.strato-rz.de`

Analysis

IP Addresses

hypersecure.cloud has two IP addresses: 217.160.0.161 and 2001:8d8:100f:f000::200

Name Servers

DNS delegation for hypersecure.cloud points to two name servers: docks02.rzone.de and shades17.rzone.de.

hypersecure.cloud at least partially shares name servers with other domains, for instance routinery.de, intamin-mobility.com, amote.de and two other.

These name servers are often used together with the name servers docks10.rzone.de, docks09.rzone.de, docks11.rzone.de and 7 other.

docks02.rzone.de directs to 217.160.80.129 and 2001:8d8:fe:53:5747:2a74:d:2. shades17.rzone.de directs to 185.132.34.144 and 2607:f1c0:fe:53:185:132:34:144. Each host name carries two IP addresses.

Mail Servers

hypersecure.cloud routes its mail through a single mail server, smtpin.rzone.de.

smtpin.rzone.de resolves to two IP numbers — 81.169.145.97 and 2a01:238:20a:202:50f0::1097.

hypersecure.cloud - robtex.com