`securecybersecurity.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns2.afternic.com` ⭐
		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	`ns1.afternic.com`
		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	`verification-d3jclucsp89ganyqbydeny.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`
TXT	`v=spf1 -all`
SOA	`ns2.afternic.com`dns@jomax.net serial=1

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

Same first word

securecybersecurity.com

DNS History

5 records (5 active, 0 former)

●NSns1.afternic.com2026-05-17 → 2026-08-03 · 2 obs

● 2026-05-17 20:50:50
● 2026-08-03 17:38:42

●NSns2.afternic.com2026-05-17 → 2026-08-03 · 2 obs

● 2026-05-17 20:50:50
● 2026-08-03 17:38:42

●NSverification-d3jclucsp89ganyqbydeny.ns101.verify.hn2026-05-17 → 2026-08-03 · 2 obs

● 2026-05-17 20:50:50
● 2026-08-03 17:38:42

●A13.248.169.482026-05-17 → 2026-08-03 · 2 obs

● 2026-05-17 20:50:50
● 2026-08-03 17:38:42

●A76.223.54.1462026-05-17 → 2026-08-03 · 2 obs

● 2026-05-17 20:50:50
● 2026-08-03 17:38:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net...	-
securecybersecurity.com	sk.s5.ans1.ns148.ztomy.com, sk.s5.ans2.ns148.ztomy.com	2 records

✅ Authoritative Response

Server:208.91.197.46

NS records: sk.s5.ans1.ns148.ztomy.com, sk.s5.ans2.ns148.ztomy.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securecybersecurity.com (unsigned zone)

⏱️ Timing

Total: 3345ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`208.91.197.46`
NS	2	`sk.s5.ans2.ns148.ztomy.com, sk.s5.ans1.ns148.ztomy.com`
MX	1	`~ (pri: 300)`
TXT	1	`v=spf1 a -all`
SOA	1	`sk.s5.ans1.ns148.ztomy.com abuse.conflue`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (sk.s5.ans1.ns148.ztomy.com, sk.s5.ans2.ns148.ztomy.com)

Analysis

IP Addresses

securecybersecurity.com points to the IP addresses 13.248.169.48 and 76.223.54.146

dfs.co, ht(0x787878).net, sswc.net and two other host names share IP numbers with securecybersecurity.com.

Name Servers

securecybersecurity.com has three name servers — ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

The name servers of securecybersecurity.com overlap at least partially with those of other domains — among them mylifestyle.net, kodadevelopment.com, 04322.com and two more.

These name servers commonly appear alongside the name servers verification-rzr7w5fcimjzspcnpdhntv.ns101.verify.hn and verification-8mgpzyd5ngxd9s7e8mlltv.ns101.verify.hn.

Each of ns1.afternic.com, ns2.afternic.com and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to two IP numbers. ns1.afternic.com points to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com points to 173.201.66.69 and 2603:5:2226::45. verification-d3jclucsp89ganyqbydeny.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.

securecybersecurity.com - robtex.com