`baltimorestrings.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@baltimorestrings.com 2026-02-05 #4

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

Same first word

baltimorestrings.com

DNS History

6 records (3 active, 3 former)

●NSns1.dyna-ns.net2026-02-23 → 2026-03-26 · 3 obs

○ 2019-12-18 07:18:06
● 2026-02-23 01:44:44
● 2026-03-26 03:06:46

○NSns13.domaincontrol.com2019-12-18 → 2019-12-18 · 3 obs

● 2019-12-18 07:18:06
○ 2026-02-23 01:44:44
○ 2026-03-26 03:06:46

○NSns14.domaincontrol.com2019-12-18 → 2019-12-18 · 3 obs

● 2019-12-18 07:18:06
○ 2026-02-23 01:44:44
○ 2026-03-26 03:06:46

●NSns2.dyna-ns.net2026-02-23 → 2026-03-26 · 3 obs

○ 2019-12-18 07:18:06
● 2026-02-23 01:44:44
● 2026-03-26 03:06:46

○A184.168.221.572019-12-18 → 2019-12-18 · 3 obs

● 2019-12-18 07:18:06
○ 2026-02-23 01:44:44
○ 2026-03-26 03:06:46

●A54.215.31.1132026-02-23 → 2026-03-26 · 3 obs

○ 2019-12-18 07:18:06
● 2026-02-23 01:44:44
● 2026-03-26 03:06:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, h.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net...	-
baltimorestrings.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.27.158

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for baltimorestrings.com (unsigned zone)

⏱️ Timing

Total: 1652ms | 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.baltimorestri`

Analysis

IP Addresses

baltimorestrings.com points to a single IP address: 54.215.31.113.

Other host names such as flightattendants.ca, sugar.lol, viralammo.com, z-o-e.com and chm.com share IP numbers with baltimorestrings.com.

Name Servers

baltimorestrings.com is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

baltimorestrings.com uses the same name server setup as other domains, including bodog24.com, siplauto.com, realscienceblogs.com, 153bet.com and kyiv.church.

Host names with four IPs

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

baltimorestrings.com - robtex.com