tampabayhca.com - robtex.com

tampabayhca.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-03-20 β†’ 2026-04-27 Β· 2 obs
● 2026-03-20 23:24:36
● 2026-04-27 20:25:22
●NSns2.medcity.net2026-03-20 β†’ 2026-04-27 Β· 2 obs
● 2026-03-20 23:24:36
● 2026-04-27 20:25:22

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net, i.gtld-servers.net...-
tampabayhca.comns1.medcity.net, ns2.medcity.net-

βœ… Authoritative Response

Server:199.91.36.20

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

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tampabayhca.com (unsigned zone)

⏱️ Timing

Total: 870ms | Queries: -

πŸ“„ Records

TypeCountSample Data

Analysis

Name Servers

tampabayhca.com's delegation uses two name servers, ns1.medcity.net and ns2.medcity.net.

tampabayhca.com shares the same name server setup as other domains, for example largomedical.com, nfloridacancertreatment.com, tampaambulatory.com, citrusmh.com and nursingmatch.com.

Host names with a single IP:

ns1.medcity.net points to 199.91.33.20.

ns2.medcity.net points to 199.91.36.20.