deepolis.de - dns.ninja

`deepolis.de`

DNSSEC	⚠️ Not signed
NS	`root-dns.netcup.net` ⚠️ Not in zone NS records
		A	2a03:4000:0:1::e1e1^{🇩🇪 netcup-AS2a03:4000::/32 NETCUP-GMBH}
			PTR	`root-dns.netcup.net`
		A	46.38.225.225^{🇩🇪 netcup-AS46.38.225.0/24}
			PTR	`root-dns.netcup.net`
NS	`second-dns.netcup.net` ⚠️ Not in zone NS records
		A	2a03:4000:2:24b::c7c7^{🇩🇪 netcup-AS2a03:4000::/32 NETCUP-GMBH}
			PTR	`second-dns.netcup.net`
		A	37.221.199.199^{🇩🇪 netcup-AS37.221.196.0/22}
			PTR	`second-dns.netcup.net`
NS	`third-dns.netcup.net` ⚠️ Not in zone NS records
		A	2a03:4001:0:106::3f44^{🇩🇪 netcup-AS2a03:4001::/32 NETCUP-GMBH}
			PTR	`third-dns.netcup.net`
		A	188.68.63.68^{🇩🇪 netcup-AS188.68.63.0/24 NETCUP-GMBH}
			PTR	`third-dns.netcup.net`

`de`

	DNSSEC	🔒 Signed (DS record present)
	NS	`f.nic.de` ⭐
	NS	`a.nic.de`
	NS	`l.de.net` ⚠️ Not in parent delegation
	NS	`n.de.net` ⚠️ Not in parent delegation
	NS	`s.de.net` ⚠️ Not in parent delegation
	NS	`z.nic.de`
	SOA	`f.nic.de`dns-operations@denic.de serial=1781355984

WOT: SAFE (79/100)

Subdomains

*.deepolis.de

Same first word

deepolis.com

deepolis.com.cn

deepolis.cn

deepolis.de

deepolis.pk

Similar names

DNS History

13 records (3 active, 10 former)

○NSns1.bigpoint.net2015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○NSns10.ns14.de2009-01-13 → 2009-01-13 · 3 obs

● 2009-01-13 07:36:02
○ 2015-05-15 23:24:20
○ 2026-06-13 13:33:44

○NSns2.bigpoint.net2015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○NSns3.bigpoint.net2015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○NSns9.ns14.de2009-01-13 → 2009-01-13 · 3 obs

● 2009-01-13 07:36:02
○ 2015-05-15 23:24:20
○ 2026-06-13 13:33:44

●NSroot-dns.netcup.net2026-02-23 → 2026-06-13 · 3 obs

○ 2017-05-18 22:34:54
● 2026-02-23 16:34:36
● 2026-06-13 13:33:44

●NSsecond-dns.netcup.net2026-02-23 → 2026-06-13 · 3 obs

○ 2017-05-18 22:34:54
● 2026-02-23 16:34:36
● 2026-06-13 13:33:44

●NSthird-dns.netcup.net2026-02-23 → 2026-06-13 · 3 obs

○ 2017-05-18 22:34:54
● 2026-02-23 16:34:36
● 2026-06-13 13:33:44

○MXmx1.bigpoint.com2009-01-13 → 2009-01-13 · 3 obs

● 2009-01-13 07:36:02
○ 2015-05-15 23:24:20
○ 2026-06-13 13:33:44

○MXmx1.bigpoint.net2015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○MXmx2.bigpoint.net2015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○A178.132.240.792015-05-15 → 2017-05-18 · 5 obs

○ 2009-01-13 07:36:02
● 2015-05-15 23:24:20
● 2017-05-18 22:34:54
○ 2026-02-23 16:34:36
○ 2026-06-13 13:33:44

○A62.146.191.872009-01-13 → 2009-01-13 · 3 obs

● 2009-01-13 07:36:02
○ 2015-05-15 23:24:20
○ 2026-06-13 13:33:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
deepolis.de	root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net	-

✅ Authoritative Response

Server:46.38.225.225

NS records: root-dns.netcup.net, second-dns.netcup.net, third-dns.netcup.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for deepolis.de (unsigned zone)

⏱️ Timing

Total: 1056ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Hierarchy

deepolis.de serves as the parent of *.deepolis.de.

Name Servers

Three name servers are authoritative for deepolis.de: root-dns.netcup.net, second-dns.netcup.net and third-dns.netcup.net.

deepolis.de has at least partial name server overlap with other domains, such as loopyball-stuttgart.de, frentic.de, clever-sim.de and two others.

root-dns.netcup.net resolves to 46.38.225.225 and 2a03:4000:0:1::e1e1. second-dns.netcup.net resolves to 37.221.199.199 and 2a03:4000:2:24b::c7c7. third-dns.netcup.net resolves to 188.68.63.68 and 2a03:4001:0:106::3f44. All three hostnames point to two IP numbers each.