ebidrx.com - dns.ninja

`ebidrx.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-e1.googledomains.com` ⭐
		A	2001:4860:4802:32::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e1.googledomains.com`
		A	216.239.32.110^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-e1.googledomains.com`
NS	`ns-cloud-e2.googledomains.com`
		A	2001:4860:4802:34::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e2.googledomains.com`
		A	216.239.34.110^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-e2.googledomains.com`
NS	`ns-cloud-e3.googledomains.com`
		A	2001:4860:4802:36::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e3.googledomains.com`
		A	216.239.36.110^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-e3.googledomains.com`
NS	`ns-cloud-e4.googledomains.com`
		A	2001:4860:4802:38::6e^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-e4.googledomains.com`
		A	216.239.38.110^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-e4.googledomains.com`
MX	`mx1.hc2781-64.iphmx.com` ⭐
		A	216.71.143.52^{🇺🇸 CISCO-1216.71.143.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	216.71.148.142^{🇺🇸 CISCO-1216.71.148.0/24 170 West Tasman Drive San Jose CA 95134 United States}
MX	`mx2.hc2781-64.iphmx.com` ⭐
		A	216.71.143.52^{🇺🇸 CISCO-1216.71.143.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	216.71.148.142^{🇺🇸 CISCO-1216.71.148.0/24 170 West Tasman Drive San Jose CA 95134 United States}
TXT	`v=spf1 include:_spf.cardinalhealth.com -all`
TXT	`MS=ms42084650`
SOA	`ns-cloud-e1.googledomains.com`cloud-dns-hostmaster@google.com serial=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=1782934136

Same first word

ebidrx.com

Similar names

redibx.com

bridex.net

debrix.com

bixder.com

bridex.de

bidrex.com

biexrd.com

dribex.com

birdex.exchange

brixed.com

riedbx.com

exbird.com

iedbrx.com

edbrix.com

bredix.com

birdex.com

bridex.ch

bridex.ca

bridex.co.uk

berdix.com

birdex.cn

deribx.com

ridebx.com

bridex.com

edbrix.org

debrix.de

DNS History

25 records (6 active, 19 former)

○NSdns1.cscdns.net2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 09:04:38
○ 2015-12-17 02:18:34
○ 2026-07-01 19:40:06

○NSdns2.cscdns.net2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 09:04:38
○ 2015-12-17 02:18:34
○ 2026-07-01 19:40:06

●NSns-cloud-e1.googledomains.com2026-02-26 → 2026-07-01 · 3 obs

○ 2021-01-11 22:48:56
● 2026-02-26 05:18:58
● 2026-07-01 19:40:06

●NSns-cloud-e2.googledomains.com2026-02-26 → 2026-07-01 · 3 obs

○ 2021-01-11 22:48:56
● 2026-02-26 05:18:58
● 2026-07-01 19:40:06

●NSns-cloud-e3.googledomains.com2026-02-26 → 2026-07-01 · 3 obs

○ 2021-01-11 22:48:56
● 2026-02-26 05:18:58
● 2026-07-01 19:40:06

●NSns-cloud-e4.googledomains.com2026-02-26 → 2026-07-01 · 3 obs

○ 2021-01-11 22:48:56
● 2026-02-26 05:18:58
● 2026-07-01 19:40:06

○NSns1.cardinalhealth.com2015-12-17 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○NSns2.cardinalhealth.com2015-12-17 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○NSns3.cardinalhealth.com2015-12-17 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○NSns4.cardinalhealth.com2015-12-17 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○NSns5.cardinalhealth.com2021-01-11 → 2021-01-11 · 4 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
○ 2026-02-26 05:18:58
○ 2026-07-01 19:40:06

○NSns6.cardinalhealth.com2021-01-11 → 2021-01-11 · 4 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
○ 2026-02-26 05:18:58
○ 2026-07-01 19:40:06

○NSns7.cardinalhealth.com2021-01-11 → 2021-01-11 · 4 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
○ 2026-02-26 05:18:58
○ 2026-07-01 19:40:06

○NSns8.cardinalhealth.com2021-01-11 → 2021-01-11 · 4 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
○ 2026-02-26 05:18:58
○ 2026-07-01 19:40:06

○NSwpec5009adins01.services.ext2021-01-11 → 2021-01-11 · 4 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
○ 2026-02-26 05:18:58
○ 2026-07-01 19:40:06

○NSwpil0219adins02.services.ext2015-12-17 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○NSwpoh0019adins02.services.ext2015-12-17 → 2017-08-31 · 7 obs

○ 2015-08-17 09:04:38
● 2015-12-17 02:18:34
● 2017-05-23 11:48:34
○ 2017-07-21 09:19:06
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

●MXmx1.hc2781-64.iphmx.com2021-01-11 → 2026-07-01 · 3 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
● 2026-07-01 19:40:06

●MXmx2.hc2781-64.iphmx.com2021-01-11 → 2026-07-01 · 3 obs

○ 2017-08-31 14:10:32
● 2021-01-11 22:48:56
● 2026-07-01 19:40:06

○MXsmtp.cardhealth.com2015-08-17 → 2017-08-31 · 4 obs

● 2015-08-17 09:04:38
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○MXsmtp2.cardinal.com2015-08-17 → 2017-08-31 · 4 obs

● 2015-08-17 09:04:38
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○MXsmtp3.cardinal.com2015-08-17 → 2017-08-31 · 4 obs

● 2015-08-17 09:04:38
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○MXsmtp4.cardinal.com2015-08-17 → 2017-08-31 · 4 obs

● 2015-08-17 09:04:38
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○MXsmtp7.cardinal.com2016-03-27 → 2017-08-31 · 5 obs

○ 2015-08-17 09:04:38
● 2016-03-27 05:25:08
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

○A209.235.101.1162015-08-17 → 2017-08-31 · 4 obs

● 2015-08-17 09:04:38
● 2017-08-31 14:10:32
○ 2021-01-11 22:48:56
○ 2026-07-01 19:40:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ebidrx.com	ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.36.110

NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ebidrx.com (unsigned zone)

⏱️ Timing

Total: 475ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-e3.googledomains.com, ns-cloud-e2.googledomains.com...`
MX	2	`mx2.hc2781-64.iphmx.com (pri: 10), mx1.hc2781-64.iphmx.com (pri: 10)`
TXT	2	`v=spf1 include:_spf.cardinalhealth.com -, MS=ms42084650`
SOA	1	`ns-cloud-e1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)

Analysis

Name Servers

The authoritative name servers for ebidrx.com are ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.

ebidrx.com has at least partial name server overlap with other domains, such as xystudio.cc, everredmayne.com, wisconsinfinancialadvisors.com and two others.

ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.

Mail Servers

Mail for ebidrx.com is handled by two mail servers — mx1.hc2781-64.iphmx.com and mx2.hc2781-64.iphmx.com.

ebidrx.com uses an identical mail server configuration to several other domains — among them uspharma.net, wavemark.net, assuramed.com and two more.

mx1.hc2781-64.iphmx.com and mx2.hc2781-64.iphmx.com each point to two IP numbers — 216.71.143.52 and 216.71.148.142 — making both hosts identical in their DNS resolution.

mx1.hc2781-64.iphmx.com along with mx2.hc2781-64.iphmx.com each resolve to 216.71.143.52 IP addresses.

mx1.hc2781-64.iphmx.com along with mx2.hc2781-64.iphmx.com each resolve to 216.71.148.142 IP addresses.