`leadvalidator.de`

DNSSEC	⚠️ Not signed
NS	`ns1.first-ns.de` ⭐
		A	2a01:4f8:0:a101::a:1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`ns1.first-ns.de`
		A	213.239.242.238^{🇩🇪 Hetzner213.239.192.0/18 HETZNER-RZ-NBG-BLK2}
			PTR	`ns1.first-ns.de`
NS	`robotns2.second-ns.de`
		A	2a01:4f8:0:1::5ddc:2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`robotns2.second-ns.de`
		A	213.133.100.103^{🇩🇪 Hetzner213.133.96.0/19 HETZNER-RZ-NBG-BLK1}
			PTR	`robotns2.second-ns.de`
NS	`robotns3.second-ns.com`
		A	2001:67c:192c::add:a3^{🇩🇪 NORIS-NETWORK2001:67c:192c::/48}
			PTR	`robotns3.second-ns.com`
		A	193.47.99.3^{🇩🇪 NORIS-NETWORK193.47.99.0/24}
			PTR	`robotns3.second-ns.com`
MX	`val1.leadvalidator.de` ⭐
		A	51.68.96.170^{🇩🇪 OVH51.68.0.0/16}
			PTR	`val1.leadvalidator.de`
TXT	`v=spf1 ip4:51.68.96.168/29 -all`
SOA	`ns1.first-ns.de`postmaster@your-server.de 2024-11-26 #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=1774863715

Subdomains

val1.leadvalidator.de

Same first word

leadvalidator.de

leadvalidator.dk

DNS History

5 records (4 active, 1 former)

●NSns1.first-ns.de2017-02-12 → 2026-03-30 · 2 obs

● 2017-02-12 06:43:04
● 2026-03-30 09:56:40

●NSrobotns2.second-ns.de2017-02-12 → 2026-03-30 · 2 obs

● 2017-02-12 06:43:04
● 2026-03-30 09:56:40

●NSrobotns3.second-ns.com2017-02-12 → 2026-03-30 · 2 obs

● 2017-02-12 06:43:04
● 2026-03-30 09:56:40

○MXmail.leadvalidator.de2017-02-12 → 2017-02-12 · 3 obs

● 2017-02-12 06:43:04
○ 2020-01-22 17:27:00
○ 2026-03-30 09:56:40

●MXval1.leadvalidator.de2020-01-22 → 2026-03-30 · 3 obs

○ 2017-02-12 06:43:04
● 2020-01-22 17:27:00
● 2026-03-30 09:56:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
leadvalidator.de	ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com	-

✅ Authoritative Response

Server:213.133.100.103

NS records: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadvalidator.de (unsigned zone)

⏱️ Timing

Total: 922ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`robotns2.second-ns.de, ns1.first-ns.de...`
MX	1	`val1.leadvalidator.de (pri: 50)`
TXT	1	`v=spf1 ip4:51.68.96.168/29 -all`
SOA	1	`ns1.first-ns.de postmaster.your-server.d`

Analysis

Hierarchy

The parent of val1.leadvalidator.de is leadvalidator.de.

Name Servers

leadvalidator.de is delegated to three name servers: robotns3.second-ns.com, ns1.first-ns.de and robotns2.second-ns.de.

leadvalidator.de partially shares name servers with other domains; examples include zhenskij-interes.ru, papagena-paycruise.de, sh3ll.de, cnbg-n.com and bitfever.net.

these name servers are commonly used with the name servers hydrogen.ns.hetzner.com.

Host names with two IP numbers:

robotns3.second-ns.com points to 2001:67c:192c::add:a3 and 193.47.99.3.

ns1.first-ns.de points to 2a01:4f8:0:a101::a:1 and 213.239.242.238.

robotns2.second-ns.de points to 2a01:4f8:0:1::5ddc:2 and 213.133.100.103.

Mail Servers

leadvalidator.de is handled by a single mail server, val1.leadvalidator.de.

val1.leadvalidator.de points to a single IP: 51.68.96.170.

leadvalidator.de - robtex.com