medicalbands.com - robtex.com
medicalbands.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=1784920897 | ||||||
Subdomains
medaserver.medicalbands.com |
Same first word
medicalbands.com |
DNS History
11 records (9 active, 2 former)
●NSivan.ns.cloudflare.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●NSuma.ns.cloudflare.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●MXalt1.aspmx.l.google.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●MXalt2.aspmx.l.google.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●MXaspmx.l.google.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●MXaspmx2.googlemail.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●MXaspmx3.googlemail.com2015-05-30 → 2026-07-24 · 2 obs
● 2026-07-24 19:33:02
●A104.21.11.412026-04-22 → 2026-07-24 · 3 obs
● 2026-04-22 00:41:00
● 2026-07-24 19:33:02
○A104.28.2.612015-05-30 → 2016-07-15 · 4 obs
● 2016-07-15 02:50:14
○ 2026-04-22 00:41:00
○ 2026-07-24 19:33:02
○A104.28.3.612015-05-30 → 2016-07-15 · 4 obs
● 2016-07-15 02:50:14
○ 2026-04-22 00:41:00
○ 2026-07-24 19:33:02
●A172.67.131.2002026-04-22 → 2026-07-24 · 3 obs
● 2026-04-22 00:41:00
● 2026-07-24 19:33:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| medicalbands.com | ivan.ns.cloudflare.com, uma.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.146
NS records: ivan.ns.cloudflare.com, uma.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 279ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.11.41, 172.67.131.200 |
| NS | 2 | ivan.ns.cloudflare.com, uma.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 0), alt1.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com include:m |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | ivan.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ivan.ns.cloudflare.com, ivan.ns.cloudflare.com, ivan.ns.cloudflare.com...)
Analysis
Hierarchy
medicalbands.com serves as the parent of medaserver.medicalbands.com.
IP Addresses
medicalbands.com resolves to the IP addresses 104.21.11.41 and 172.67.131.200
Among the host names that share IP numbers with medicalbands.com are top10saunas.com, purestart.nl, babes55.com and two others.
Name Servers
medicalbands.com has two authoritative name servers — ivan.ns.cloudflare.com and uma.ns.cloudflare.com.
medicalbands.com has the same name server delegation as a number of other domains, such as sinofsx.org, complexearth.com, richutc.com and two more.
medicalbands.com has at least partial name server overlap with other domains, such as sobellaw.com, alpha-vico.com, nnx.be and two others.
It is common to see these name servers used together with name servers erin.ns.cloudflare.com and rachel.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
ivan.ns.cloudflare.com points to 108.162.193.120, 172.64.33.120, 173.245.59.120 and 3 other IP addresses.
uma.ns.cloudflare.com points to 108.162.192.146, 172.64.32.146, 173.245.58.146 and 3 other IP addresses.
Mail Servers
medicalbands.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
medicalbands.com shares at least some of its mail servers with other domains — for example cannaculturecollective.com, ns500758.ns500759.ns500759.ns500736.ns500698.ns500698.ns500735.ns500736.ns500576.ns500708.ns500698.ns500686.ns500619.trackreceptor.com, ns500699.ns500734.ns500734.ns500734.ns500693.ns500699.ns500699.ns500588.ns500699.ns500588.ns500632.ns500588.ns500632.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com resolves to 142.251.179.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 2a00:1450:400b:c02::1a IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.26 IP addresses.