`trafficfirewall.com`

DNSSEC	⚠️ Not signed
A	54.215.31.113^{🇺🇸 Amazon54.215.0.0/17 EC2 SFO prefix}
		PTR	`ec2-54-215-31-113.us-west-1.compute.amazonaws.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@trafficfirewall.com 2026-04-24 #2

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

Same first word

trafficfirewall.com

DNS History

7 records (3 active, 4 former)

○NSns.123-reg.co.uk2017-05-07 → 2017-05-07 · 3 obs

● 2017-05-07 22:50:56
○ 2026-03-30 03:34:44
○ 2026-04-26 08:48:02

●NSns1.dyna-ns.net2026-03-30 → 2026-04-26 · 3 obs

○ 2017-05-07 22:50:56
● 2026-03-30 03:34:44
● 2026-04-26 08:48:02

○NSns2.123-reg.co.uk2017-05-07 → 2017-05-07 · 3 obs

● 2017-05-07 22:50:56
○ 2026-03-30 03:34:44
○ 2026-04-26 08:48:02

●NSns2.dyna-ns.net2026-03-30 → 2026-04-26 · 3 obs

○ 2017-05-07 22:50:56
● 2026-03-30 03:34:44
● 2026-04-26 08:48:02

○MXmail.trafficfirewall.com2017-05-07 → 2017-05-07 · 3 obs

● 2017-05-07 22:50:56
○ 2026-03-30 03:34:44
○ 2026-04-26 08:48:02

○A185.135.9.2102017-05-07 → 2017-05-07 · 3 obs

● 2017-05-07 22:50:56
○ 2026-03-30 03:34:44
○ 2026-04-26 08:48:02

●A54.215.31.1132026-03-30 → 2026-04-26 · 3 obs

○ 2017-05-07 22:50:56
● 2026-03-30 03:34:44
● 2026-04-26 08:48:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, e.gtld-servers.net...	-
trafficfirewall.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.26.92

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for trafficfirewall.com (unsigned zone)

⏱️ Timing

Total: 389ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.215.31.113`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.trafficfirewa`

Analysis

IP Addresses

trafficfirewall.com resolves to a single IP address: 54.215.31.113.

Other host names including 868b.cc, nano.agency, caglini.me, mcataid.com and kpedo.com share IP numbers with trafficfirewall.com.

Name Servers

trafficfirewall.com's delegation uses two name servers, ns1.dyna-ns.net and ns2.dyna-ns.net.

trafficfirewall.com shares the same name server setup as other domains, for example fury-sro.com, anmq6by5.xyz, svidjamise.info, raunitschke.net and 821gmail.com.

trafficfirewall.com at least partially shares name servers with other domains; for instance zo2zo.com.

Host names with four IP numbers:

ns1.dyna-ns.net points to 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158.

ns2.dyna-ns.net points to 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.

trafficfirewall.com - robtex.com