`containerdienst-service.de`

DNSSEC	⚠️ Not signed
A	185.53.179.136^{🇩🇪 TEAMINTERNET-AS185.53.179.0/24 Registration for Team Internet by Next Dimension}
NS	`ina1.registrar.eu` ⭐
		A	2606:4700:52::ac40:3465^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.52.101^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ina2.registrar.eu`
		A	2606:4700:52::ac40:3465^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.52.101^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ina3.registrar.eu`
		A	2606:4700:5a::ac40:3516^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.53.22^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ina1.registrar.eu`noreply@registrar.eu 2016-12-20 #0

`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=1786157545

⚠️ On DNS blocklist: tif

Same first word

containerdienst-service.de

DNS History

10 records (4 active, 6 former)

●NSina1.registrar.eu2026-04-08 → 2026-08-08 · 3 obs

○ 2026-04-05 02:06:40
● 2026-04-08 12:02:26
● 2026-08-08 03:10:56

●NSina2.registrar.eu2026-04-08 → 2026-08-08 · 3 obs

○ 2026-04-05 02:06:40
● 2026-04-08 12:02:26
● 2026-08-08 03:10:56

●NSina3.registrar.eu2026-04-08 → 2026-08-08 · 3 obs

○ 2026-04-05 02:06:40
● 2026-04-08 12:02:26
● 2026-08-08 03:10:56

○NSmeg.ns.cloudflare.com2026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

○NSthaddeus.ns.cloudflare.com2026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

○A104.21.62.1982026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

○A172.67.138.1942026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

●A185.53.179.1362026-04-08 → 2026-08-08 · 3 obs

○ 2026-04-05 02:06:40
● 2026-04-08 12:02:26
● 2026-08-08 03:10:56

○A2606:4700:3030::ac43:8ac22026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

○A2606:4700:3036::6815:3ec62026-03-20 → 2026-04-05 · 4 obs

● 2026-03-20 09:37:50
● 2026-04-05 02:06:40
○ 2026-04-08 12:02:26
○ 2026-08-08 03:10:56

🔍 DNS Trace

Analysis

IP Addresses

containerdienst-service.de resolves to one IP address: 185.53.179.136.

mail.jip.mobi, 164c28e8-289b-4b27-8322-883663e8020f.overviewopenai.com, snosdoma.ru and two other host names share IP numbers with containerdienst-service.de.

Name Servers

containerdienst-service.de is served by three name servers: ina1.registrar.eu, ina2.registrar.eu and ina3.registrar.eu.

containerdienst-service.de has at least partial name server overlap with other domains, such as net0.librered.com, panera-breadmenu.com, www.mondial-relance-suivi-client.com and two others.

ina1.registrar.eu and ina2.registrar.eu both direct to 172.64.52.101 and 2606:4700:52::ac40:3465, while ina3.registrar.eu directs to 172.64.53.22 and 2606:4700:5a::ac40:3516; all three hostnames resolve to two IP numbers.

ina1.registrar.eu and ina2.registrar.eu each have 2606:4700:52::ac40:3465 IP addresses.

ina1.registrar.eu and ina2.registrar.eu each have 172.64.52.101 IP addresses.

containerdienst-service.de - robtex.com