`layer7-security.to`

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	`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	`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`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net serial=1

`to`

	DNSSEC	⚠️ Not signed
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1785466218

⚠️ On DNS blocklist: tif

Same first word

layer7-security.to

DNS History

10 records (4 active, 6 former)

○NScleo.ns.cloudflare.com2020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

○NSjo.ns.cloudflare.com2020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

●NSns1.afternic.com2026-07-26 → 2026-07-31 · 3 obs

○ 2020-04-07 15:39:22
● 2026-07-26 01:10:02
● 2026-07-31 03:02:28

●NSns2.afternic.com2026-07-26 → 2026-07-31 · 3 obs

○ 2020-04-07 15:39:22
● 2026-07-26 01:10:02
● 2026-07-31 03:02:28

○A104.31.70.1862020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

○A104.31.71.1862020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

●A13.248.169.482026-07-26 → 2026-07-31 · 3 obs

○ 2020-04-07 15:39:22
● 2026-07-26 01:10:02
● 2026-07-31 03:02:28

○A2606:4700:3032::681f:47ba2020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

○A2606:4700:3036::681f:46ba2020-04-07 → 2020-04-07 · 3 obs

● 2020-04-07 15:39:22
○ 2026-07-26 01:10:02
○ 2026-07-31 03:02:28

●A76.223.54.1462026-07-26 → 2026-07-31 · 3 obs

○ 2020-04-07 15:39:22
● 2026-07-26 01:10:02
● 2026-07-31 03:02:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
to	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
layer7-security.to	ns1.afternic.com, ns2.afternic.com	-

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for to (unsigned zone)

⏱️ Timing

Total: 1277ms | 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: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)

Analysis

IP Addresses

layer7-security.to directs to two IP numbers, 13.248.169.48 and 76.223.54.146

qjm.co, herkevimmusic.mudawin.com, wont.shop plus two other host names have IP numbers in common with layer7-security.to.

Name Servers

layer7-security.to has two authoritative name servers — ns1.afternic.com and ns2.afternic.com.

The name server configuration of layer7-security.to is shared with other domains, for instance sharpword.com, empanada.net, hostmaster.hubeasy.com and two others.

layer7-security.to has at least partial name server overlap with other domains, such as prinset.com, join(0x736578).com, jwuz.com and two others.

It is common to find these name servers paired with the name servers verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn, verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-df6xaksrcxynprww8hzsaa.ns101.verify.hn.

Both ns1.afternic.com and ns2.afternic.com have two IP addresses each. 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.

layer7-security.to - robtex.com