`securesystemsai.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-ttgutf5pjoxkrnjbkbimes.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=1784536127

Same first word

securesystemsai.com

DNS History

5 records (5 active, 0 former)

●NSns1.afternic.com2026-05-18 → 2026-07-20 · 2 obs

● 2026-05-18 11:10:22
● 2026-07-20 08:40:36

●NSns2.afternic.com2026-05-18 → 2026-07-20 · 2 obs

● 2026-05-18 11:10:22
● 2026-07-20 08:40:36

●NSverification-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn2026-05-18 → 2026-07-20 · 2 obs

● 2026-05-18 11:10:22
● 2026-07-20 08:40:36

●A13.248.169.482026-05-18 → 2026-07-20 · 2 obs

● 2026-05-18 11:10:22
● 2026-07-20 08:40:36

●A76.223.54.1462026-05-18 → 2026-07-20 · 2 obs

● 2026-05-18 11:10:22
● 2026-07-20 08:40:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
securesystemsai.com	ns1.afternic.com, ns2.afternic.com, verification-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com, verification-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securesystemsai.com (unsigned zone)

⏱️ Timing

Total: 3209ms | 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`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

securesystemsai.com has two IP addresses: 13.248.169.48 and 76.223.54.146

Additional host names — methuenmassachusetts.com, mail.aristides.gr, mx.texas-holdem-online.com and two others — share IP numbers with securesystemsai.com.

Name Servers

securesystemsai.com is delegated to three name servers: ns1.afternic.com, ns2.afternic.com and verification-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn.

The name servers of securesystemsai.com overlap at least partially with those of other domains — among them himlook.com, web3vegas.com, yuzumi.com and two more.

These name servers commonly appear in combination with the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.

ns1.afternic.com, ns2.afternic.com and verification-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn 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-ttgutf5pjoxkrnjbkbimes.ns101.verify.hn resolves to 13.248.169.48 and 76.223.54.146.

securesystemsai.com - robtex.com