securitychecks.de - dns.ninja

`securitychecks.de`

DNSSEC	⚠️ Not signed
NS	`a.ns14.net` ⭐
		A	2001:8d8:fe:53:217:160:80:160^{🇩🇪 IONOS-AS2001:8d8:fe::/47 IONOS AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.de`
		A	217.160.80.160^{🇩🇪 IONOS-AS217.160.80.0/22 AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.de`
NS	`b.ns14.net`
		A	2001:8d8:fe:53:217:160:81:160^{🇩🇪 IONOS-AS2001:8d8:fe::/47 IONOS AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.biz`
		A	217.160.81.160^{🇩🇪 IONOS-AS217.160.80.0/22 AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.biz`
NS	`c.ns14.net`
		A	2607:f1c0:fe:53:185:132:35:160^{🇺🇸 IONOS-ANYCAST2607:f1c0:fe::/47 AS8560 global anycast services (more specific) 1&1 IONOS Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
			PTR	`ns-ix1.ui-dns.org`
		A	185.132.35.160^{🇩🇪 IONOS-ANYCAST185.132.32.0/22 IONOS DNSAS (eBGP DNS)}
			PTR	`ns-ix1.ui-dns.org`
NS	`d.ns14.net`
		A	2607:f1c0:fe:53:185:132:34:160^{🇺🇸 IONOS-ANYCAST2607:f1c0:fe::/47 AS8560 global anycast services (more specific) 1&1 IONOS Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
			PTR	`ns-ix1.ui-dns.com`
		A	185.132.34.160^{🇩🇪 IONOS-ANYCAST185.132.32.0/22 IONOS DNSAS (eBGP DNS)}
			PTR	`ns-ix1.ui-dns.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 -all`
SOA	`a.ns14.net`do-not-reply@securitychecks.de 2022-12-04 #3

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

Same first word

securitychecks.de

securitychecks.net

DNS History

15 records (9 active, 6 former)

●NSa.ns14.net2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●NSb.ns14.net2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●NSc.ns14.net2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●NSd.ns14.net2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

○NSns1-tec.de2015-07-05 → 2020-01-19 · 4 obs

● 2015-07-05 13:26:18
● 2020-01-19 12:06:20
○ 2026-03-25 01:23:32
○ 2026-07-13 12:39:02

○NSns2-tec.de2015-07-05 → 2020-01-19 · 4 obs

● 2015-07-05 13:26:18
● 2020-01-19 12:06:20
○ 2026-03-25 01:23:32
○ 2026-07-13 12:39:02

●MXalt1.aspmx.l.google.com2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●MXalt2.aspmx.l.google.com2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●MXalt3.aspmx.l.google.com2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●MXalt4.aspmx.l.google.com2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

●MXaspmx.l.google.com2026-03-25 → 2026-07-13 · 3 obs

○ 2020-01-19 12:06:20
● 2026-03-25 01:23:32
● 2026-07-13 12:39:02

○MXmx1.securemail.name2015-07-05 → 2020-01-19 · 4 obs

● 2015-07-05 13:26:18
● 2020-01-19 12:06:20
○ 2026-03-25 01:23:32
○ 2026-07-13 12:39:02

○MXmx2.securemail.name2015-07-05 → 2020-01-19 · 4 obs

● 2015-07-05 13:26:18
● 2020-01-19 12:06:20
○ 2026-03-25 01:23:32
○ 2026-07-13 12:39:02

○A176.9.19.2472015-07-05 → 2017-02-16 · 4 obs

● 2015-07-05 13:26:18
● 2017-02-16 09:57:16
○ 2020-01-19 12:06:20
○ 2026-07-13 12:39:02

○A45.67.71.522020-01-19 → 2020-01-19 · 4 obs

○ 2017-02-16 09:57:16
● 2020-01-19 12:06:20
○ 2026-03-25 01:23:32
○ 2026-07-13 12:39:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	f.nic.de, z.nic.de, a.nic.de	-
securitychecks.de	a.ns14.net, d.ns14.net, c.ns14.net, b.ns14.net	-

✅ Authoritative Response

Server:217.160.81.160

NS records: a.ns14.net, d.ns14.net, c.ns14.net, b.ns14.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securitychecks.de (unsigned zone)

⏱️ Timing

Total: 1448ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`d.ns14.net, c.ns14.net...`
MX	5	`alt4.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 -all`
SOA	1	`a.ns14.net do-not-reply.securitychecks.d`

Analysis

Name Servers

Four name servers handle the delegation for securitychecks.de: a.ns14.net, b.ns14.net, c.ns14.net and d.ns14.net.

securitychecks.de partially shares its NS delegation with several other domains, including thomann.events, minibag.at, vintageportalen.se and two others.

a.ns14.net, b.ns14.net, c.ns14.net and d.ns14.net each carry two IP addresses. a.ns14.net has 217.160.80.160 and 2001:8d8:fe:53:217:160:80:160; b.ns14.net has 217.160.81.160 and 2001:8d8:fe:53:217:160:81:160; c.ns14.net has 185.132.35.160 and 2607:f1c0:fe:53:185:132:35:160; d.ns14.net has 185.132.34.160 and 2607:f1c0:fe:53:185:132:34:160.

Mail Servers

securitychecks.de is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by securitychecks.de are shared with other domains: ns500758.ns500759.ns500759.ns500758.ns500735.ns500736.ns500736.ns500708.ns500576.ns500576.ns500576.ns500576.trackreceptor.com, ns500742.ns500671.ns500671.ns500671.ns500704.ns500704.ns500671.ns500705.ns500705.ns500291.ns500291.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500698.ns500758.ns500698.ns500759.ns500735.ns500698.ns500735.ns500698.ns500735.ns500735.ns500698.ns500652.ns500576.ns500576.trackreceptor.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 142.251.167.27 and 2607:f8b0:4004:c23::1b.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.