emedicinal.com - dns.ninja

`emedicinal.com`

DNSSEC	⚠️ Not signed
A	204.197.246.14^{🇺🇸 PRIVATESYSTEMS204.197.240.0/21 PrivateSystems Networks TX}
		PTR	`host.ticketspire.com`
NS	`ns1.ticketspire.com` ⭐ ⚠️ Not in parent delegation
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
NS	`ns1.emedicinal.com` ⚠️ Not in zone NS records
NS	`ns2.emedicinal.com` ⚠️ Not in zone NS records
NS	`ns2.ticketspire.com` ⚠️ Not in parent delegation
		A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
		A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-223-25-84.compute-1.amazonaws.com`
		A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-117-197.compute-1.amazonaws.com`
MX	`emedicinal.com` ⭐
		A	204.197.246.14^{🇺🇸 PRIVATESYSTEMS204.197.240.0/21 PrivateSystems Networks TX}
			PTR	`host.ticketspire.com`
TXT	`v=spf1 ip4:69.73.181.140 ip4:65.254.44.67 ip4:66.246.218.170 a mx a:neptune.n...`
SOA	`ns1.ticketspire.com`sales@ticketspire.com 2026-06-29 #1

`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=1785872539

MX for

emedicinal.com

Same first word

emedicinal.com

Similar names

DNS History

9 records (6 active, 3 former)

●NSns1.emedicinal.com2026-03-07 → 2026-08-04 · 3 obs

○ 2018-01-09 11:00:36
● 2026-03-07 02:26:44
● 2026-08-04 19:44:04

●NSns1.ticketspire.com2026-03-07 → 2026-08-04 · 3 obs

○ 2018-01-09 11:00:36
● 2026-03-07 02:26:44
● 2026-08-04 19:44:04

●NSns2.emedicinal.com2026-03-07 → 2026-08-04 · 3 obs

○ 2018-01-09 11:00:36
● 2026-03-07 02:26:44
● 2026-08-04 19:44:04

●NSns2.ticketspire.com2026-03-07 → 2026-08-04 · 3 obs

○ 2018-01-09 11:00:36
● 2026-03-07 02:26:44
● 2026-08-04 19:44:04

○NSvns1.nocdirect.com2015-07-31 → 2018-01-09 · 4 obs

● 2015-07-31 22:55:06
● 2018-01-09 11:00:36
○ 2026-03-07 02:26:44
○ 2026-08-04 19:44:04

○NSvns2.nocdirect.com2015-07-31 → 2018-01-09 · 4 obs

● 2015-07-31 22:55:06
● 2018-01-09 11:00:36
○ 2026-03-07 02:26:44
○ 2026-08-04 19:44:04

●MXemedicinal.com2015-07-31 → 2026-08-04 · 2 obs

● 2015-07-31 22:55:06
● 2026-08-04 19:44:04

●A204.197.246.142026-03-07 → 2026-08-04 · 3 obs

○ 2018-01-09 11:00:36
● 2026-03-07 02:26:44
● 2026-08-04 19:44:04

○A69.73.181.162015-07-31 → 2018-01-09 · 4 obs

● 2015-07-31 22:55:06
● 2018-01-09 11:00:36
○ 2026-03-07 02:26:44
○ 2026-08-04 19:44:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
emedicinal.com	ns1.emedicinal.com, ns2.emedicinal.com	2 records

✅ Authoritative Response

Server:204.197.246.14

NS records: ns1.emedicinal.com, ns2.emedicinal.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for emedicinal.com (unsigned zone)

⏱️ Timing

Total: 128ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`204.197.246.14`
NS	2	`ns1.ticketspire.com, ns2.ticketspire.com`
MX	1	`emedicinal.com (pri: 0)`
TXT	1	`v=spf1 ip4:69.73.181.140 ip4:65.254.44.6`
SOA	1	`ns1.ticketspire.com sales.ticketspire.co`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.emedicinal.com, ns2.emedicinal.com)

Analysis

Mail Server Role

emedicinal.com serves as a mail server for emedicinal.com.

IP Addresses

emedicinal.com has exactly one IP address — 204.197.246.14.

Host names like voobs.com are further examples that share IP numbers with emedicinal.com.

Name Servers

Four name servers handle the delegation for emedicinal.com: ns1.emedicinal.com, ns2.emedicinal.com, ns1.ticketspire.com and ns2.ticketspire.com.

emedicinal.com is at least partially co-delegated on name servers with other domains, such as voobs.com.

These name servers tend to be deployed in combination with the name servers ns1.voobs.com and ns2.voobs.com.

Both ns1.ticketspire.com and ns2.ticketspire.com resolve to four IP addresses: ns1.ticketspire.com points to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee while ns2.ticketspire.com resolves to 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

ns1.ticketspire.com along with ns2.ticketspire.com each resolve to 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb IP addresses.

ns1.ticketspire.com along with ns2.ticketspire.com each resolve to 2600:1f18:4ae:c606:78d4:4260:db4e:aeee IP addresses.

ns1.ticketspire.com along with ns2.ticketspire.com each resolve to 13.223.25.84 IP addresses.

ns1.ticketspire.com along with ns2.ticketspire.com each resolve to 54.243.117.197 IP addresses.

Mail Servers

emedicinal.com uses exactly one mail server, which is emedicinal.com.

emedicinal.com carries a single IP number, which is 204.197.246.14.