callmedline.com - robtex.com

callmedline.com

DNSSEC⚠️ Not signed
NSns1.medcity.net ⚠️ Not in zone NS records
A199.91.33.20πŸ‡ΊπŸ‡Έ AS14626199.91.33.0/24
PTRns1.medcity.net
NSns2.medcity.net ⚠️ Not in zone NS records
A199.91.36.20πŸ‡ΊπŸ‡Έ AS14626199.91.36.0/24
PTRns2.medcity.net

com

Same first word

DNS History

2 records (2 active, 0 former)

NSns1.medcity.netns2.medcity.net
●NSns1.medcity.net2026-02-15 β†’ 2026-03-27 Β· 2 obs
● 2026-02-15 16:06:42
● 2026-03-27 05:50:06
●NSns2.medcity.net2026-02-15 β†’ 2026-03-27 Β· 2 obs
● 2026-02-15 16:06:42
● 2026-03-27 05:50:06

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
callmedline.comns1.medcity.net, ns2.medcity.net-

βœ… Authoritative Response

Server:199.91.33.20

NS records: ns1.medcity.net, ns2.medcity.net

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for callmedline.com (unsigned zone)

⏱️ Timing

Total: 528ms | Queries: -

πŸ“„ Records

TypeCountSample Data

Analysis

Name Servers

callmedline.com's delegation uses two name servers: ns1.medcity.net and ns2.medcity.net.

callmedline.com uses the same name server setup as other domains, such as mcchildrenshospital.com, doctors-hospital.com, gcmedical.net, mdnearu.com and fortwaltonpedser.com.

Host names with a single IP address: ns1.medcity.net points to 199.91.33.20; ns2.medcity.net points to 199.91.36.20.