wearablexp.com - robtex.com
wearablexp.com
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=1785069387 | ||||||
Same first word
wearablexp.com |
DNS History
11 records (11 active, 0 former)
โNSlindsey.ns.cloudflare.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โNSnero.ns.cloudflare.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โMXalt1.aspmx.l.google.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โMXalt2.aspmx.l.google.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โMXalt3.aspmx.l.google.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โMXalt4.aspmx.l.google.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โMXaspmx.l.google.com2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โA104.21.91.282026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โA172.67.165.902026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โA2606:4700:3031::ac43:a55a2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
โA2606:4700:3036::6815:5b1c2026-07-13 โ 2026-07-26 ยท 2 obs
โ 2026-07-26 12:41:16
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| wearablexp.com | lindsey.ns.cloudflare.com, nero.ns.cloudflare.com | 12 records |
โ Authoritative Response
Server:108.162.195.28
NS records: lindsey.ns.cloudflare.com, nero.ns.cloudflare.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for wearablexp.com (unsigned zone)
โฑ๏ธ Timing
Total: 210ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.91.28, 172.67.165.90 |
| AAAA | 2 | 2606:4700:3031::ac43:a55a, 2606:4700:3036::6815:5b1c |
| NS | 2 | lindsey.ns.cloudflare.com, nero.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | google-site-verification=0DZv0WEXNMFu7g9, google-site-verification=cxMoH16Eqeipa0M... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | lindsey.ns.cloudflare.com dns.cloudflare |
๐ Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com, lindsey.ns.cloudflare.com...)
Analysis
IP Addresses
wearablexp.com points to the four IP addresses 104.21.91.28, 172.67.165.90, 2606:4700:3031::ac43:a55a and 2606:4700:3036::6815:5b1c.
Among the host names that share IP numbers with wearablexp.com are pegipegi.id, www.fd0808.com, qsbdsm.com and two others.
Name Servers
wearablexp.com uses two name servers for its delegation: lindsey.ns.cloudflare.com and nero.ns.cloudflare.com.
wearablexp.com has the same name server delegation as a number of other domains, such as piloty.fr, svk.ac.th, komunity.eu and two more.
The name servers of wearablexp.com overlap at least partially with those of other domains โ among them xxchu.cn, pirenquixa.sbs, pl-oferta4006176.click and two more.
These name servers commonly co-occur with the name servers jarred.ns.cloudflare.com, chan.ns.cloudflare.com, wells.ns.cloudflare.com and rosalie.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
Hostname lindsey.ns.cloudflare.com directs to 108.162.194.5, 162.159.38.5 and 172.64.34.5 along with 3 other IP addresses.
Hostname nero.ns.cloudflare.com directs to 108.162.195.28, 162.159.44.28 and 172.64.35.28 along with 3 other IP addresses.
Mail Servers
wearablexp.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
wearablexp.com shares at least some of its mail servers with other domains โ for example ns500698.ns500758.ns500759.ns500759.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500619.ns500576.trackreceptor.com, ns500765.ns500699.ns500699.ns500693.ns500699.ns500699.ns500699.ns500699.ns500588.ns500693.ns500683.ns500699.ns500699.ns500683.ns500612.ns500110.dtrkdll.com, ns500765.ns500699.ns500699.ns500693.ns500734.ns500588.ns500693.ns500683.ns500683.ns500588.ns500588.ns500588.ns500588.ns500588.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 172.253.139.26 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.