`ciemedcr.com`

DNSSEC	⚠️ Not signed
A	64.20.44.83^{🇺🇸 NJIIX-1}
		PTR	`rose.xeedcore.com`
NS	`ns1.dnsxeed.com` ⭐ ⚠️ Not in parent delegation
		A	149.28.241.149^{🇺🇸 AS-VULTR}
			PTR	`ns1.hosting506.com`
		A	216.238.71.36^{🇲🇽 AS-VULTR}
			PTR	`ns1.hosting506.com`
NS	`ns1.hosting506.com` ⚠️ Not in zone NS records 🔒
		A	149.28.241.149^{🇺🇸 AS-VULTR}
			PTR	`ns1.hosting506.com`
		A	216.238.71.36^{🇲🇽 AS-VULTR}
			PTR	`ns1.hosting506.com`
NS	`ns2.dnsxeed.com` ⚠️ Not in parent delegation
		A	45.77.162.45^{🇺🇸 AS-VULTR}
			PTR	`ns2.hosting506.com`
		A	216.219.90.25^{🇺🇸 RoadRunner}
NS	`ns2.hosting506.com` ⚠️ Not in zone NS records 🔒
		A	45.77.162.45^{🇺🇸 AS-VULTR}
			PTR	`ns2.hosting506.com`
		A	216.219.90.25^{🇺🇸 RoadRunner}
NS	`ns3.dnsxeed.com` ⚠️ Not in parent delegation
		A	149.28.91.195^{🇺🇸 AS-VULTR}
			PTR	`ns3.hosting506.com`
NS	`ns3.hosting506.com` ⚠️ Not in zone NS records 🔒
		A	149.28.91.195^{🇺🇸 AS-VULTR}
			PTR	`ns3.hosting506.com`
NS	`ns4.dnsxeed.com` ⚠️ Not in parent delegation
		A	149.28.52.3^{🇺🇸 AS-VULTR}
			PTR	`ns4.hosting506.com`
NS	`ns4.hosting506.com` ⚠️ Not in zone NS records 🔒
		A	149.28.52.3^{🇺🇸 AS-VULTR}
			PTR	`ns4.hosting506.com`
MX	`mail.ciemedcr.com` ⭐
		A	64.20.44.83^{🇺🇸 NJIIX-1}
			PTR	`rose.xeedcore.com`
TXT	`v=spf1 +a +mx +ip4:64.20.44.83 include:relay.mailchannels.net ~all`
SOA	`ns1.dnsxeed.com`rose@xeedcore.com 2026-01-22 #6

`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.net`nstld@verisign-grs.com serial=1771291435

Previously MX for

ciemedcr.com

Up

mail.ciemedcr.com

Same first word

ciemedcr.com

DNS History

20 records (10 active, 10 former)

○NSns1.consultoriascr.com2018-08-18 → 2018-08-18 · 4 obs

○ 2017-02-06 15:04:38
● 2018-08-18 21:50:32
○ 2026-02-21 04:15:02
○ 2026-02-21 10:45:22

●NSns1.dnsxeed.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

●NSns1.hosting506.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

○NSns1.nsresponse.com2017-02-06 → 2017-02-06 · 4 obs

○ 2016-03-17 07:58:56
● 2017-02-06 15:04:38
○ 2018-08-18 21:50:32
○ 2026-02-21 10:45:22

○NSns1.ryvsolutions.com2015-08-19 → 2016-03-17 · 4 obs

● 2015-08-19 04:28:06
● 2016-03-17 07:58:56
○ 2017-02-06 15:04:38
○ 2026-02-21 10:45:22

○NSns2.consultoriascr.com2018-08-18 → 2018-08-18 · 4 obs

○ 2017-02-06 15:04:38
● 2018-08-18 21:50:32
○ 2026-02-21 04:15:02
○ 2026-02-21 10:45:22

●NSns2.dnsxeed.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

●NSns2.hosting506.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

○NSns2.nsresponse.com2017-02-06 → 2017-02-06 · 4 obs

○ 2016-03-17 07:58:56
● 2017-02-06 15:04:38
○ 2018-08-18 21:50:32
○ 2026-02-21 10:45:22

○NSns2.ryvsolutions.com2015-08-19 → 2016-03-17 · 4 obs

● 2015-08-19 04:28:06
● 2016-03-17 07:58:56
○ 2017-02-06 15:04:38
○ 2026-02-21 10:45:22

●NSns3.dnsxeed.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

●NSns3.hosting506.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

●NSns4.dnsxeed.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

●NSns4.hosting506.com2026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

○MXciemedcr.com2018-08-18 → 2018-08-18 · 4 obs

○ 2017-02-06 15:04:38
● 2018-08-18 21:50:32
○ 2026-02-21 04:15:02
○ 2026-02-21 10:45:22

●MXmail.ciemedcr.com2015-08-19 → 2026-02-21 · 5 obs

● 2015-08-19 04:28:06
● 2017-02-06 15:04:38
○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

○A204.93.177.1382017-02-06 → 2017-02-06 · 4 obs

○ 2016-03-17 07:58:56
● 2017-02-06 15:04:38
○ 2018-08-18 21:50:32
○ 2026-02-21 10:45:22

○A205.251.134.992015-08-19 → 2016-03-17 · 4 obs

● 2015-08-19 04:28:06
● 2016-03-17 07:58:56
○ 2017-02-06 15:04:38
○ 2026-02-21 10:45:22

○A209.50.49.422018-08-18 → 2018-08-18 · 4 obs

○ 2017-02-06 15:04:38
● 2018-08-18 21:50:32
○ 2026-02-21 04:15:02
○ 2026-02-21 10:45:22

●A64.20.44.832026-02-21 → 2026-02-21 · 3 obs

○ 2018-08-18 21:50:32
● 2026-02-21 04:15:02
● 2026-02-21 10:45:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ciemedcr.com	ns1.hosting506.com, ns2.hosting506.com, ns3.hosting506.com, ns4.hosting506.com	6 records

✅ Authoritative Response

Server: 149.28.241.149

NS records: ns1.hosting506.com, ns2.hosting506.com, ns3.hosting506.com, ns4.hosting506.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ciemedcr.com (unsigned zone)

⏱️ Timing

Total: 202ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.20.44.83`
NS	4	`ns1.dnsxeed.com, ns4.dnsxeed.com...`
MX	1	`mail.ciemedcr.com (pri: 10)`
TXT	1	`v=spf1 +a +mx +ip4:64.20.44.83 include:r`
SOA	1	`ns1.dnsxeed.com rose.xeedcore.com`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.hosting506.com, ns1.hosting506.com, ns2.hosting506.com...)

AI analysis

ciemedcr.com is the parent of mail.ciemedcr.com.

ciemedcr.com resolves to one IP number: 64.20.44.83.

other host names including mail.seprosalud.com, mail.ciemedcr.com, seprosalud.com, k-9internacional.com and osminvargas.com share IP numbers with ciemedcr.com.

ciemedcr.com is delegated to eight name servers: ns1.dnsxeed.com, ns2.dnsxeed.com, ns3.dnsxeed.com, ns4.dnsxeed.com, ns1.hosting506.com, ns2.hosting506.com, ns3.hosting506.com and ns4.hosting506.com.

ciemedcr.com at least partially shares name servers with other domains, for instance consultoriayconstruccioncr.com, seprosalud.com, assetscr.com, grupocarara.com and bun-ca.org.

these name servers are commonly used alongside ns5.hosting506.com.

Host names with two IP numbers:

ns1.dnsxeed.com points to: 149.28.241.149 and 216.238.71.36.

ns2.dnsxeed.com points to: 45.77.162.45 and 216.219.90.25.

ns1.hosting506.com points to: 149.28.241.149 and 216.238.71.36.

ns2.hosting506.com points to: 45.77.162.45 and 216.219.90.25.

Host names with one IP number:

ns3.dnsxeed.com points to: 149.28.91.195.

ns4.dnsxeed.com points to: 149.28.52.3.

ns3.hosting506.com points to: 149.28.91.195.

ns4.hosting506.com points to: 149.28.52.3.

Host names that point to 149.28.241.149: ns1.dnsxeed.com and ns1.hosting506.com.

Host names that point to 216.238.71.36: ns1.dnsxeed.com and ns1.hosting506.com.

Host names that point to 45.77.162.45: ns2.dnsxeed.com and ns2.hosting506.com.

Host names that point to 216.219.90.25: ns2.dnsxeed.com and ns2.hosting506.com.

Host names that point to 149.28.91.195: ns3.dnsxeed.com and ns3.hosting506.com.

Host names that point to 149.28.52.3: ns4.dnsxeed.com and ns4.hosting506.com.

ciemedcr.com is handled by a single mail server, mail.ciemedcr.com.

mail.ciemedcr.com resolves to IP 64.20.44.83.

ciemedcr.com - robtex.com

ciemedcr.com

com

Previously MX for

Up

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

AI analysis

`ciemedcr.com`

`com`