baltimorewatch.com - robtex.com
baltimorewatch.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.152.147🇺🇸 Amazon3.33.144.0/20 | ||||||
| PTR | a4ec4c6ea1c92e2e6.awsglobalaccelerator.com | ||||||
| A | 15.197.142.173🇺🇸 Amazon15.197.128.0/20 | ||||||
| NS | ns35.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21b1::12🇺🇸 GODADDY-DNS2603:5:21b0::/44 | ||||||
| PTR | ns35.domaincontrol.com | ||||||
| A | 97.74.107.18🇺🇸 GODADDY-DNS97.74.106.0/23 | ||||||
| PTR | ns35.domaincontrol.com | ||||||
| NS | ns36.domaincontrol.com | ||||||
| A | 2603:5:22b1::12🇺🇸 GODADDY-DNS2603:5:22b0::/44 | ||||||
| PTR | ns36.domaincontrol.com | ||||||
| A | 173.201.75.18🇺🇸 GODADDY-DNS173.201.74.0/23 | ||||||
| PTR | ns36.domaincontrol.com | ||||||
| SOA | ns35.domaincontrol.comdns@jomax.net 2021-10-16 #0 | ||||||
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.netnstld@verisign-grs.com serial=1774407527 | ||||||
Same first word
baltimorewatch.com |
Similar names
DNS History
4 records (4 active, 0 former)
●NSns35.domaincontrol.com2026-02-19 → 2026-03-25 · 2 obs
● 2026-03-25 03:17:36
●NSns36.domaincontrol.com2026-02-19 → 2026-03-25 · 2 obs
● 2026-03-25 03:17:36
●A15.197.142.1732026-02-19 → 2026-03-25 · 2 obs
● 2026-03-25 03:17:36
●A3.33.152.1472026-02-19 → 2026-03-25 · 2 obs
● 2026-03-25 03:17:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net... | - |
| baltimorewatch.com | ns35.domaincontrol.com, ns36.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.75.18
NS records: ns35.domaincontrol.com, ns36.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for baltimorewatch.com (unsigned zone)
⏱️ Timing
Total: 828ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.142.173, 3.33.152.147 |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| SOA | 1 | ns35.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)
Analysis
IP Addresses
baltimorewatch.com resolves to two IP numbers: 3.33.152.147 and 15.197.142.173.
Other host names, for instance vforand.com, marshallhockey.org, shailu.me, madisonlowerbackpain.com and starofsarah.com share IP numbers with baltimorewatch.com.
Name Servers
Two name servers ns35.domaincontrol.com and ns36.domaincontrol.com handle delegation for baltimorewatch.com.
baltimorewatch.com uses the same name server setup as other domains, for example macps.co.uk, triptik.co.uk, rd-wireless.com, scottlooper.com and jaceviate.com.
Host names with two IP numbers:
ns35.domaincontrol.com points to: 2603:5:21b1::12 and 97.74.107.18
ns36.domaincontrol.com points to: 2603:5:22b1::12 and 173.201.75.18