stents.com - robtex.com
stents.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.cardinalhealth.com ⚠️ Not in zone NS records | ||||||
| A | 216.239.32.110🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns-cloud-e1.googledomains.com | ||||||
| NS | ns2.cardinalhealth.com ⚠️ Not in zone NS records | ||||||
| A | 216.239.34.110🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns-cloud-e2.googledomains.com | ||||||
| NS | ns3.cardinalhealth.com ⚠️ Not in zone NS records | ||||||
| A | 216.239.36.110🇺🇸 Google216.239.36.0/24 | ||||||
| PTR | ns-cloud-e3.googledomains.com | ||||||
| NS | ns4.cardinalhealth.com ⚠️ Not in zone NS records | ||||||
| A | 216.239.38.110🇺🇸 Google216.239.38.0/24 | ||||||
| PTR | ns-cloud-e4.googledomains.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=1786019844 | ||||||
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NSns1.cardinalhealth.com2026-07-16 → 2026-08-06 · 3 obs
● 2026-07-16 19:50:20
● 2026-08-06 12:40:10
○NSns1.jnj.com2015-07-17 → 2016-05-02 · 4 obs
● 2016-05-02 17:56:30
○ 2026-07-16 19:50:20
○ 2026-08-06 12:40:10
●NSns2.cardinalhealth.com2026-07-16 → 2026-08-06 · 3 obs
● 2026-07-16 19:50:20
● 2026-08-06 12:40:10
●NSns3.cardinalhealth.com2026-07-16 → 2026-08-06 · 3 obs
● 2026-07-16 19:50:20
● 2026-08-06 12:40:10
○NSns3.jnj.com2015-07-17 → 2016-05-02 · 4 obs
● 2016-05-02 17:56:30
○ 2026-07-16 19:50:20
○ 2026-08-06 12:40:10
●NSns4.cardinalhealth.com2026-07-16 → 2026-08-06 · 3 obs
● 2026-07-16 19:50:20
● 2026-08-06 12:40:10
○NSns5.jnj.com2015-07-17 → 2016-05-02 · 4 obs
● 2016-05-02 17:56:30
○ 2026-07-16 19:50:20
○ 2026-08-06 12:40:10
○A148.177.17.232015-07-17 → 2016-05-02 · 4 obs
● 2016-05-02 17:56:30
○ 2026-07-16 19:50:20
○ 2026-08-06 12:40:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| stents.com | ns1.cardinalhealth.com, ns2.cardinalhealth.com, ns3.cardinalhealth.com, ns4.cardinalhealth.com | 4 records |
✅ Authoritative Response
Server:216.239.38.110
NS records: ns1.cardinalhealth.com, ns2.cardinalhealth.com, ns3.cardinalhealth.com, ns4.cardinalhealth.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stents.com (unsigned zone)
⏱️ Timing
Total: 197ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.cardinalhealth.com, ns2.cardinalhealth.com, ns3.cardinalhealth.com...)
Analysis
Name Servers
stents.com has four authoritative name servers: ns1.cardinalhealth.com, ns2.cardinalhealth.com, ns3.cardinalhealth.com and ns4.cardinalhealth.com.
At least some of stents.com's name servers are shared with other domains, for example cordis.es, optapro.us, stents.biz and two more.
These name servers are often deployed together with the name servers ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
ns1.cardinalhealth.com, ns2.cardinalhealth.com, ns3.cardinalhealth.com and ns4.cardinalhealth.com each resolve to one IP address: ns1.cardinalhealth.com resolves to 216.239.32.110, ns2.cardinalhealth.com resolves to 216.239.34.110, ns3.cardinalhealth.com resolves to 216.239.36.110 and ns4.cardinalhealth.com resolves to 216.239.38.110.