`wearablemonitor.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	`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

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

Same first word

wearablemonitor.com

DNS History

9 records (4 active, 5 former)

●NSns1.afternic.com2026-03-11 → 2026-03-25 · 3 obs

○ 2019-12-24 00:42:26
● 2026-03-11 14:09:02
● 2026-03-25 19:59:28

○NSns1.dnsaddress.com2015-05-15 → 2017-03-30 · 4 obs

● 2015-05-15 19:40:52
● 2017-03-30 00:30:22
○ 2019-12-24 00:42:26
○ 2026-03-25 19:59:28

○NSns1.fabulous.com2019-12-24 → 2019-12-24 · 4 obs

○ 2017-03-30 00:30:22
● 2019-12-24 00:42:26
○ 2026-03-11 14:09:02
○ 2026-03-25 19:59:28

●NSns2.afternic.com2026-03-11 → 2026-03-25 · 3 obs

○ 2019-12-24 00:42:26
● 2026-03-11 14:09:02
● 2026-03-25 19:59:28

○NSns2.fabulous.com2019-12-24 → 2019-12-24 · 4 obs

○ 2017-03-30 00:30:22
● 2019-12-24 00:42:26
○ 2026-03-11 14:09:02
○ 2026-03-25 19:59:28

●A13.248.169.482026-03-11 → 2026-03-25 · 3 obs

○ 2019-12-24 00:42:26
● 2026-03-11 14:09:02
● 2026-03-25 19:59:28

○A157.230.161.2212019-12-24 → 2019-12-24 · 4 obs

○ 2017-03-30 00:30:22
● 2019-12-24 00:42:26
○ 2026-03-11 14:09:02
○ 2026-03-25 19:59:28

○A23.23.174.1322015-05-15 → 2017-03-30 · 4 obs

● 2015-05-15 19:40:52
● 2017-03-30 00:30:22
○ 2019-12-24 00:42:26
○ 2026-03-25 19:59:28

●A76.223.54.1462026-03-11 → 2026-03-25 · 3 obs

○ 2019-12-24 00:42:26
● 2026-03-11 14:09:02
● 2026-03-25 19:59:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
wearablemonitor.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:173.201.66.69

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wearablemonitor.com (unsigned zone)

⏱️ Timing

Total: 172ms | 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	`ns2.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

wearablemonitor.com resolves to two IPs: 13.248.169.48 and 76.223.54.146.

other host names for instance bolechowice.com, www.inevio.com, zombiefrog.com, audiomatics.com and wated.com share IP numbers with wearablemonitor.com.

Name Servers

wearablemonitor.com is delegated to two name servers: ns1.afternic.com and ns2.afternic.com.

wearablemonitor.com shares the same name server setup as other domains, for example zpoom.com, kentut.com, wuhan.us, www.escortview.com and forgiven.net.

wearablemonitor.com at least partially shares name servers with other domains, for instance neosky.co.uk, dpym.com, session.me, envirowise.com and georgespaul.com.

These name servers are often used with verification-kychg6v62cjy2sq3kx5ou5.ns101.verify.hn and verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn.

Host names with two IP numbers:

ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69

ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69

wearablemonitor.com - robtex.com