telehealthprotocol.com - robtex.com
telehealthprotocol.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.130.190🇺🇸 Amazon3.33.128.0/20 | ||||||
| PTR | a2aa9ff50de748dbe.awsglobalaccelerator.com | ||||||
| A | 15.197.148.33🇺🇸 Amazon15.197.144.0/20 | ||||||
| NS | ns67.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2174::2c🇺🇸 GODADDY-DNS2603:5:2170::/44 | ||||||
| PTR | ns67.domaincontrol.com | ||||||
| A | 97.74.103.44🇺🇸 GODADDY-DNS97.74.102.0/23 | ||||||
| PTR | ns67.domaincontrol.com | ||||||
| NS | ns68.domaincontrol.com | ||||||
| A | 2603:5:2274::2c🇺🇸 GODADDY-DNS2603:5:2270::/44 | ||||||
| PTR | ns68.domaincontrol.com | ||||||
| A | 173.201.71.44🇺🇸 GODADDY-DNS173.201.70.0/23 | ||||||
| PTR | ns68.domaincontrol.com | ||||||
| SOA | ns67.domaincontrol.comdns@jomax.net 2026-01-26 #0 | ||||||
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=1774596977 | ||||||
Same first word
telehealthprotocol.com |
DNS History
4 records (4 active, 0 former)
●NSns67.domaincontrol.com2026-02-16 → 2026-03-27 · 2 obs
● 2026-03-27 07:52:26
●NSns68.domaincontrol.com2026-02-16 → 2026-03-27 · 2 obs
● 2026-03-27 07:52:26
●A15.197.148.332026-02-16 → 2026-03-27 · 2 obs
● 2026-03-27 07:52:26
●A3.33.130.1902026-02-16 → 2026-03-27 · 2 obs
● 2026-03-27 07:52:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net, j.gtld-servers.net... | - |
| telehealthprotocol.com | ns67.domaincontrol.com, ns68.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.103.44
NS records: ns67.domaincontrol.com, ns68.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telehealthprotocol.com (unsigned zone)
⏱️ Timing
Total: 296ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns67.domaincontrol.com, ns68.domaincontrol.com |
| SOA | 1 | ns67.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)
Analysis
IP Addresses
The entity telehealthprotocol.com points to two IP numbers: 3.33.130.190 and 15.197.148.33.
For instance, other host names myiambic.com, sailfete.mobi, adstuf.com, nessasview.com and jenniferbharper.com share IP numbers with telehealthprotocol.com.
Name Servers
telehealthprotocol.com is delegated to two name servers: ns67.domaincontrol.com and ns68.domaincontrol.com.
telehealthprotocol.com uses the same name server setup as other domains such as aloegloe.com, klmukapps.co.uk, dol.co.uk, closet-fashionista.com and gastroenterologo.mx.
Host names with two IP numbers:
ns67.domaincontrol.com points to 2603:5:2174::2c and 97.74.103.44; ns68.domaincontrol.com points to 2603:5:2274::2c and 173.201.71.44.