`managed-connectivity.com`

DNSSEC	⚠️ Not signed
NS	`pns.dtag.de` ⭐
		A	2003:40:8000::100^{🇩🇪 DTAG2003::/19 Deutsche Telekom large PA space}
			PTR	`pns.dtag.de`
		A	194.25.0.125^{🇩🇪 DTAG194.25.0.0/16 Deutsche Telekom AG, Internet service provider}
			PTR	`pns.dtag.de`
NS	`ns1.telekom.net`
		A	2003:180:a:1000::53^{🇩🇪 DTAG2003::/19 Deutsche Telekom large PA space}
			PTR	`ns1.telekom.net`
		A	212.185.24.65^{🇩🇪 DTAG212.184.0.0/15 Deutsche Telekom AG, Internet service provider}
			PTR	`ns1.telekom.net`
SOA	`pns.dtag.de`dnsadmin@nic.dtag.de 2022-08-03 #0

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1783227006

Same first word

managed-connectivity.de

managed-connectivity.com

DNS History

7 records (2 active, 5 former)

●NSns1.telekom.net2026-04-14 → 2026-07-05 · 3 obs

○ 2021-06-09 22:48:52
● 2026-04-14 02:29:16
● 2026-07-05 05:09:06

●NSpns.dtag.de2017-01-04 → 2026-07-05 · 2 obs

● 2017-01-04 20:21:22
● 2026-07-05 05:09:06

○NSsecondary007.dtag.net2017-01-04 → 2021-06-09 · 4 obs

● 2017-01-04 20:21:22
● 2021-06-09 22:48:52
○ 2026-04-14 02:29:16
○ 2026-07-05 05:09:06

○MXmail.managed-connectivity.com2021-06-09 → 2021-06-09 · 4 obs

○ 2017-01-04 20:21:22
● 2021-06-09 22:48:52
○ 2026-04-14 02:29:16
○ 2026-07-05 05:09:06

○MXwww.managed-connectivity.com2017-01-04 → 2021-06-09 · 4 obs

● 2017-01-04 20:21:22
● 2021-06-09 22:48:52
○ 2026-04-14 02:29:16
○ 2026-07-05 05:09:06

○A185.181.12.262021-06-09 → 2021-06-09 · 4 obs

○ 2017-12-20 22:03:20
● 2021-06-09 22:48:52
○ 2026-04-14 02:29:16
○ 2026-07-05 05:09:06

○A89.31.0.382017-01-04 → 2017-12-20 · 4 obs

● 2017-01-04 20:21:22
● 2017-12-20 22:03:20
○ 2021-06-09 22:48:52
○ 2026-07-05 05:09:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
managed-connectivity.com	pns.dtag.de, ns1.telekom.net	-

✅ Authoritative Response

Server:212.185.24.65

NS records: pns.dtag.de, ns1.telekom.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for managed-connectivity.com (unsigned zone)

⏱️ Timing

Total: 3894ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.telekom.net, pns.dtag.de`
SOA	1	`pns.dtag.de dnsadmin.nic.dtag.de`

Analysis

Name Servers

The NS records for managed-connectivity.com delegate to pns.dtag.de and ns1.telekom.net.

managed-connectivity.com shares its NS records with other domains, for example balkonentwaesserungen.de, warsteiner-uk.com, tmobileadvantage.com and two others.

There is at least partial name server overlap between managed-connectivity.com and other domains — 29.128.87.in-addr.arpa, 128.159.62.in-addr.arpa, 37.190.87.in-addr.arpa and two more among them.

These name servers regularly appear alongside secondary006.dtag.net, secondary007.dtag.net, ns0.niedersachsen.com and 4 other name servers in NS record sets.

pns.dtag.de resolves to 194.25.0.125 and 2003:40:8000::100. Likewise, ns1.telekom.net resolves to 212.185.24.65 and 2003:180:a:1000::53 — two IP addresses apiece.

managed-connectivity.com - robtex.com