`bayareareporting.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`
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=1786532964

Same first word

bayareareporting.com

DNS History

22 records (4 active, 18 former)

○NSdns010.d.register.com2015-06-08 → 2015-10-31 · 4 obs

● 2015-06-08 10:33:38
● 2015-10-31 05:00:04
○ 2016-02-10 15:22:30
○ 2026-08-12 11:35:46

○NSdns025.c.register.com2015-06-08 → 2015-10-31 · 4 obs

● 2015-06-08 10:33:38
● 2015-10-31 05:00:04
○ 2016-02-10 15:22:30
○ 2026-08-12 11:35:46

○NSdns188.b.register.com2015-06-08 → 2015-10-31 · 4 obs

● 2015-06-08 10:33:38
● 2015-10-31 05:00:04
○ 2016-02-10 15:22:30
○ 2026-08-12 11:35:46

○NSdns200.a.register.com2015-06-08 → 2015-10-31 · 4 obs

● 2015-06-08 10:33:38
● 2015-10-31 05:00:04
○ 2016-02-10 15:22:30
○ 2026-08-12 11:35:46

●NSns1.afternic.com2026-03-31 → 2026-08-12 · 3 obs

○ 2018-08-13 04:39:50
● 2026-03-31 19:41:06
● 2026-08-12 11:35:46

○NSns1.bodis.com2026-03-31 → 2026-08-12 · 2 obs

○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

○NSns1.uniregistrymarket.link2018-08-13 → 2018-08-13 · 4 obs

○ 2017-01-24 13:14:18
● 2018-08-13 04:39:50
○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

●NSns2.afternic.com2026-03-31 → 2026-08-12 · 3 obs

○ 2018-08-13 04:39:50
● 2026-03-31 19:41:06
● 2026-08-12 11:35:46

○NSns2.bodis.com2026-03-31 → 2026-08-12 · 2 obs

○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

○NSns2.uniregistrymarket.link2018-08-13 → 2018-08-13 · 4 obs

○ 2017-01-24 13:14:18
● 2018-08-13 04:39:50
○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

○NSsk.s5.ans1.ns122.ztomy.com2017-01-24 → 2017-01-24 · 4 obs

○ 2016-05-03 23:25:42
● 2017-01-24 13:14:18
○ 2018-08-13 04:39:50
○ 2026-08-12 11:35:46

○NSsk.s5.ans2.ns122.ztomy.com2017-01-24 → 2017-01-24 · 4 obs

○ 2016-05-03 23:25:42
● 2017-01-24 13:14:18
○ 2018-08-13 04:39:50
○ 2026-08-12 11:35:46

○NSsk.s5.cm.ns1.37.ztomy.com2016-02-10 → 2016-05-03 · 5 obs

○ 2015-10-31 05:00:04
● 2016-02-10 15:22:30
● 2016-05-03 23:25:42
○ 2017-01-24 13:14:18
○ 2026-08-12 11:35:46

○NSsk.s5.cm.ns2.37.ztomy.com2016-02-10 → 2016-05-03 · 5 obs

○ 2015-10-31 05:00:04
● 2016-02-10 15:22:30
● 2016-05-03 23:25:42
○ 2017-01-24 13:14:18
○ 2026-08-12 11:35:46

●A13.248.169.482026-03-31 → 2026-08-12 · 3 obs

○ 2018-08-13 04:39:50
● 2026-03-31 19:41:06
● 2026-08-12 11:35:46

○A199.59.243.2282026-03-31 → 2026-08-12 · 2 obs

○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

○A208.91.197.442017-01-24 → 2017-01-24 · 4 obs

○ 2016-05-03 23:25:42
● 2017-01-24 13:14:18
○ 2018-08-13 04:39:50
○ 2026-08-12 11:35:46

○A208.91.197.542016-02-10 → 2016-05-03 · 5 obs

○ 2015-10-31 05:00:04
● 2016-02-10 15:22:30
● 2016-05-03 23:25:42
○ 2017-01-24 13:14:18
○ 2026-08-12 11:35:46

○A209.237.152.182015-06-08 → 2015-10-31 · 4 obs

● 2015-06-08 10:33:38
● 2015-10-31 05:00:04
○ 2016-02-10 15:22:30
○ 2026-08-12 11:35:46

○A69.172.201.1532018-08-13 → 2018-08-13 · 4 obs

○ 2017-01-24 13:14:18
● 2018-08-13 04:39:50
○ 2026-03-31 19:41:06
○ 2026-08-12 11:35:46

●A76.223.54.1462026-03-31 → 2026-08-12 · 3 obs

○ 2018-08-13 04:39:50
● 2026-03-31 19:41:06
● 2026-08-12 11:35:46

○PTRsk.s5.ans1.ns122.ztomy.com2017-01-24 → 2017-01-24 · 3 obs

● 2017-01-24 13:14:18
○ 2018-08-13 04:39:50
○ 2026-08-12 11:35:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bayareareporting.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:97.74.98.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bayareareporting.com (unsigned zone)

⏱️ Timing

Total: 123ms | 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

bayareareporting.com points to the IP addresses 13.248.169.48 and 76.223.54.146

1.crutch.com, neutrix.com, attiredagentic.xyz and two other host names share IP numbers with bayareareporting.com.

Name Servers

bayareareporting.com has two authoritative name servers — ns1.afternic.com and ns2.afternic.com.

bayareareporting.com uses the same name servers as several other domains — among them strategicbenefits.net, kitchenathome.com, www.www.by26.com and two more.

The name servers of bayareareporting.com overlap at least partially with those of other domains — among them tecnam.us, aeropark.org, techbeast.co.uk and two more.

The name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-d3jclucsp89ganyqbydeny.ns101.verify.hn and verification-qxu9bfdaih4cxurbbn3f4d.ns101.verify.hn are commonly seen alongside these name servers.

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.

bayareareporting.com - robtex.com