securitykey.net - dns.ninja

`securitykey.net`

DNSSEC	⚠️ Not signed
NS	`ns1.afternic.com` ⚠️ Not in zone NS records
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com` ⚠️ Not in zone NS records
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
NS	`verification-4a5f06ab.ns3.dan.hosting` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
NS	`verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`

`net`

	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=1785639447

Subdomains

nullmx.securitykey.net

Same first word

securitykey.com

securitykey.xyz

securitykey.ru

securitykey.net

securitykey.it

securitykey.nl

Similar names

keysecurity.com.br

keysecurity.xyz

keysecurity.net

keysecurity.ch

keysecurity.ru

keysecurity.com

keysecurity.at

keysecurity.co

keysecurity.com.tw

keysecurity.com.au

DNS History

19 records (4 active, 15 former)

●NSns1.afternic.com2026-04-04 → 2026-08-02 · 3 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
● 2026-08-02 03:08:36

○NSns1.hitfarm.com2007-10-12 → 2007-10-12 · 3 obs

● 2007-10-12 03:40:32
○ 2015-06-25 01:17:26
○ 2026-08-02 03:08:36

●NSns2.afternic.com2026-04-04 → 2026-08-02 · 3 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
● 2026-08-02 03:08:36

○NSns2.hitfarm.com2007-10-12 → 2007-10-12 · 3 obs

● 2007-10-12 03:40:32
○ 2015-06-25 01:17:26
○ 2026-08-02 03:08:36

○NSns3.hitfarm.com2007-10-12 → 2007-10-12 · 3 obs

● 2007-10-12 03:40:32
○ 2015-06-25 01:17:26
○ 2026-08-02 03:08:36

○NSns73.domaincontrol.com2015-06-25 → 2016-01-19 · 5 obs

○ 2007-10-12 03:40:32
● 2015-06-25 01:17:26
● 2016-01-19 14:39:46
○ 2016-04-16 03:10:28
○ 2026-08-02 03:08:36

○NSns74.domaincontrol.com2015-06-25 → 2016-01-19 · 5 obs

○ 2007-10-12 03:40:32
● 2015-06-25 01:17:26
● 2016-01-19 14:39:46
○ 2016-04-16 03:10:28
○ 2026-08-02 03:08:36

○NSpdns07.domaincontrol.com2016-04-16 → 2017-06-26 · 5 obs

○ 2016-01-19 14:39:46
● 2016-04-16 03:10:28
● 2017-06-26 17:36:48
○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

○NSpdns08.domaincontrol.com2016-04-16 → 2017-06-26 · 5 obs

○ 2016-01-19 14:39:46
● 2016-04-16 03:10:28
● 2017-06-26 17:36:48
○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

●NSverification-4a5f06ab.ns3.dan.hosting2026-04-04 → 2026-08-02 · 3 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
● 2026-08-02 03:08:36

●NSverification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn2026-04-04 → 2026-08-02 · 3 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
● 2026-08-02 03:08:36

○MX.2026-04-04 → 2026-08-02 · 2 obs

○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

○MXmailstore1.secureserver.net2015-06-25 → 2017-06-26 · 5 obs

○ 2007-10-12 03:40:32
● 2015-06-25 01:17:26
● 2017-06-26 17:36:48
○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

○MXnullmx.securitykey.net2007-10-12 → 2007-10-12 · 3 obs

● 2007-10-12 03:40:32
○ 2015-06-25 01:17:26
○ 2026-08-02 03:08:36

○MXsmtp.secureserver.net2015-06-25 → 2017-06-26 · 5 obs

○ 2007-10-12 03:40:32
● 2015-06-25 01:17:26
● 2017-06-26 17:36:48
○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

○A13.248.169.482026-04-04 → 2026-04-04 · 4 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
○ 2026-08-01 19:36:00
○ 2026-08-02 03:08:36

○A184.168.221.312015-06-25 → 2017-06-26 · 5 obs

○ 2007-10-12 03:40:32
● 2015-06-25 01:17:26
● 2017-06-26 17:36:48
○ 2026-04-04 03:02:46
○ 2026-08-02 03:08:36

○A64.40.116.352007-10-12 → 2007-10-12 · 3 obs

● 2007-10-12 03:40:32
○ 2015-06-25 01:17:26
○ 2026-08-02 03:08:36

○A76.223.54.1462026-04-04 → 2026-04-04 · 4 obs

○ 2017-06-26 17:36:48
● 2026-04-04 03:02:46
○ 2026-08-01 19:36:00
○ 2026-08-02 03:08:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, e.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net...	-
securitykey.net	ns1.afternic.com, ns2.afternic.com, verification-4a5f06ab.ns3.dan.hosting, verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn	-

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-4a5f06ab.ns3.dan.hosting, verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securitykey.net (unsigned zone)

⏱️ Timing

Total: 3243ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

Analysis

Hierarchy

securitykey.net is a parent domain of nullmx.securitykey.net.

Name Servers

securitykey.net has four authoritative name servers: ns1.afternic.com, ns2.afternic.com, verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn and verification-4a5f06ab.ns3.dan.hosting.

securitykey.net shares at least some of its name servers with other domains, including apxco.com, dlraw.com, ugww.com and two others.

These name servers are frequently paired with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn and verification-jh56ag3qoy8fsktzvbvfht.ns101.verify.hn.

The hostnames ns1.afternic.com, ns2.afternic.com, verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn and verification-4a5f06ab.ns3.dan.hosting each resolve to two IP addresses. ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45; ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45; verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn and verification-4a5f06ab.ns3.dan.hosting both resolve to 13.248.169.48 and 76.223.54.146.

These two host names — verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn and verification-4a5f06ab.ns3.dan.hosting — each point to 13.248.169.48 IP addresses.

These two host names — verification-sw3szqhk9w7yzwvhnzbumx.ns101.verify.hn and verification-4a5f06ab.ns3.dan.hosting — each point to 76.223.54.146 IP addresses.