`germancongress.com`

DNSSEC	⚠️ Not signed
NS	`ns19.domaincontrol.com` ⭐
		A	2603:5:21d0::a^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns19.domaincontrol.com`
		A	97.74.109.10^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns19.domaincontrol.com`
NS	`ns20.domaincontrol.com`
		A	2603:5:22d0::a^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns20.domaincontrol.com`
		A	173.201.77.10^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns20.domaincontrol.com`
MX	`mx0.germancongress.com` ⭐
		A	80.237.138.5^{🇩🇪 GD-EMEA-DC-CGN180.237.138.0/24 GD MASS Network}
			PTR	`mx0.webpack.hosteurope.de`
TXT	`v=spf1 a mx include:spf.server-he.de -all`
SOA	`ns19.domaincontrol.com`dns@jomax.net 2026-03-07 #0

`com`

	DNSSEC	⚠️ Not signed
	NS	`dns1.qti.com` ⚠️ Not in zone NS records

Subdomains

mx0.germancongress.com

DNS History

10 records (3 active, 7 former)

○NSns1.deutschlandkongress.de2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 18:06:10
○ 2015-07-18 16:33:20
○ 2026-04-04 23:15:52

○NSns1.hans.hosteurope.de2015-07-18 → 2017-11-17 · 4 obs

○ 2008-03-17 18:06:10
● 2015-07-18 16:33:20
● 2017-11-17 17:22:24
○ 2026-04-04 23:15:52

●NSns19.domaincontrol.com2026-04-04 → 2026-04-04 · 2 obs

○ 2017-11-17 17:22:24
● 2026-04-04 23:15:52

○NSns2.deutschlandkongress.de2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 18:06:10
○ 2015-07-18 16:33:20
○ 2026-04-04 23:15:52

○NSns2.hans.hosteurope.de2015-07-18 → 2017-11-17 · 4 obs

○ 2008-03-17 18:06:10
● 2015-07-18 16:33:20
● 2017-11-17 17:22:24
○ 2026-04-04 23:15:52

●NSns20.domaincontrol.com2026-04-04 → 2026-04-04 · 2 obs

○ 2017-11-17 17:22:24
● 2026-04-04 23:15:52

●MXmx0.germancongress.com2015-07-18 → 2026-04-04 · 3 obs

○ 2008-03-17 18:06:10
● 2015-07-18 16:33:20
● 2026-04-04 23:15:52

○MXmx3.provider4u.de2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 18:06:10
○ 2015-07-18 16:33:20
○ 2026-04-04 23:15:52

○A5.35.226.1602017-11-17 → 2017-11-17 · 3 obs

○ 2016-11-25 13:03:58
● 2017-11-17 17:22:24
○ 2026-04-04 23:15:52

○A80.237.133.1602015-07-18 → 2016-11-25 · 5 obs

○ 2008-03-17 18:06:10
● 2015-07-18 16:33:20
● 2016-11-25 13:03:58
○ 2017-11-17 17:22:24
○ 2026-04-04 23:15:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net, h.gtld-servers.net...	-
germancongress.com	ns19.domaincontrol.com, ns20.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.109.10

NS records: ns19.domaincontrol.com, ns20.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for germancongress.com (unsigned zone)

⏱️ Timing

Total: 33ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns19.domaincontrol.com, ns20.domaincontrol.com`
MX	1	`mx0.germancongress.com (pri: 50)`
TXT	1	`v=spf1 a mx include:spf.server-he.de -al`
SOA	1	`ns19.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)

Analysis

Hierarchy

germancongress.com is the parent of mx0.germancongress.com.

Name Servers

germancongress.com is delegated to two name servers ns19.domaincontrol.com and ns20.domaincontrol.com.

germancongress.com shares the same name server setup as other domains, for instance maestrosdelasador.com, allbrandedgroup.com.au, rtlsshop.com, meyerla.com and courtneygolf.com.

Host names with two IP numbers:

The host name ns19.domaincontrol.com points to 2603:5:21d0::a and 97.74.109.10; the host name ns20.domaincontrol.com points to 2603:5:22d0::a and 173.201.77.10.

Mail Servers

germancongress.com is handled by a single mail server, mx0.germancongress.com.

mx0.germancongress.com resolves to IP 80.237.138.5.

germancongress.com - robtex.com