claims.concernservices.com - robtex.com
claims.concernservices.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.68.236.220🇺🇸 RoadRunner216.68.236.0/24 ARIN Route Object for FUSE customer TriHealth | ||||||
| PTR | trihealth-bethesda-hospital-216-68-236-220.static.fuse.net | ||||||
concernservices.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.68.236.68🇺🇸 RoadRunner216.68.236.0/24 ARIN Route Object for FUSE customer TriHealth | ||||||
| NS | ns1-09.azure-dns.com ⭐ | ||||||
| NS | ns2-09.azure-dns.net | ||||||
| NS | ns3-09.azure-dns.org | ||||||
| NS | ns4-09.azure-dns.info | ||||||
| SOA | ns1-09.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
Same first word
Similar names
DNS History
1 record (1 active, 0 former)
●A216.68.236.2202015-08-18 → 2026-03-25 · 2 obs
● 2015-08-18 09:19:56
● 2026-03-25 04:49:18
● 2026-03-25 04:49:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net... | - |
| concernservices.com | ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info | 2 records |
✅ Authoritative Response
Server:150.171.21.9
NS records: ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for concernservices.com (unsigned zone)
⏱️ Timing
Total: 190ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.68.236.220 |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-09.azure-dns.com, ns1-09.azure-dns.com)
Analysis
IP Addresses
claims.concernservices.com points to a single IP address: 216.68.236.220.
Other host names, for instance trihealth-bethesda-hospital-216-68-236-220.static.fuse.net, share IP numbers with claims.concernservices.com.