ridium.com - dns.ninja

`ridium.com`

DNSSEC	⚠️ Not signed
A	216.40.47.17^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
		PTR	`redirect.managednsservice.com`
NS	`ns1.mdnsservice.com` ⭐
		A	2604:4000:0:d:216:40:47:18^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.mdnsservice.com`
		A	216.40.47.18^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.mdnsservice.com`
NS	`ns2.mdnsservice.com`
		A	2604:4000:2800:d:64:99:148:11^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.mdnsservice.com`
		A	64.98.148.11^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.mdnsservice.com`
NS	`ns3.mdnsservice.com`
		A	2604:4000:0:d:64:99:96:34^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.mdnsservice.com`
		A	64.99.96.34^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.mdnsservice.com`
MX	`ridium-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::a^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr21cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm5pr04cu00103.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch4pr04cu00102.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.10.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr03cu00202.inbound.protection.outlook.com`
		A	52.101.10.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr05cu00102.inbound.protection.outlook.com`
		A	52.101.41.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00305.inbound.protection.outlook.com`
TXT	`ouva5npl5lca6gb9t59k6u0ic1`
TXT	`MS=ms91334403`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`u84qg8oo0llqj369nvhfnmf555`
TXT	`m729om3m0lurbp20tmonfsia99`
SOA	`ns1.mdnsservice.com`hostmaster@mdnsservice.com serial=2805538412

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

Same first word

ridium.ru

ridium.com

ridium.co.uk

Similar names

irdium.de

muridi.com

rumidi.ru

iridum.sk

driium.com

iridum.com

iridum.eu

imidur.com

iridum.de

imudir.com

rumidi.com

dirimu.com

idrium.org

dirium.com

iridum.pl

irdium.com

idrium.com

mudrii.com

dimuri.com

udimir.com

idrium.net

udimri.com

imurid.com

durimi.com

DNS History

6 records (5 active, 1 former)

●NSns1.mdnsservice.com2015-05-23 → 2026-08-09 · 2 obs

● 2015-05-23 16:22:00
● 2026-08-09 20:23:08

●NSns2.mdnsservice.com2015-05-23 → 2026-08-09 · 2 obs

● 2015-05-23 16:22:00
● 2026-08-09 20:23:08

●NSns3.mdnsservice.com2015-05-23 → 2026-08-09 · 2 obs

● 2015-05-23 16:22:00
● 2026-08-09 20:23:08

○MXmx.ridium.com2015-05-23 → 2017-02-13 · 4 obs

● 2015-05-23 16:22:00
● 2017-02-13 05:33:06
○ 2020-02-18 01:20:14
○ 2026-08-09 20:23:08

●MXridium-com.mail.protection.outlook.com2020-02-18 → 2026-08-09 · 3 obs

○ 2017-02-13 05:33:06
● 2020-02-18 01:20:14
● 2026-08-09 20:23:08

●A216.40.47.172015-05-23 → 2026-08-09 · 2 obs

● 2015-05-23 16:22:00
● 2026-08-09 20:23:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
ridium.com	ns1.mdnsservice.com, ns2.mdnsservice.com, ns3.mdnsservice.com	6 records

✅ Authoritative Response

Server:216.40.47.18

NS records: ns1.mdnsservice.com, ns2.mdnsservice.com, ns3.mdnsservice.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ridium.com (unsigned zone)

⏱️ Timing

Total: 288ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.40.47.17`
NS	3	`ns1.mdnsservice.com, ns2.mdnsservice.com...`
MX	1	`ridium-com.mail.protection.outlook.com (`
TXT	5	`ouva5npl5lca6gb9t59k6u0ic1, MS=ms91334403...`
SOA	1	`ns1.mdnsservice.com hostmaster.mdnsservi`

📌 Glue Records Collected

Total: 6

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

Analysis

IP Addresses

ridium.com resolves to just one IP address, 216.40.47.17.

Two other host names, along with sofnmetaldesigns.com, authorcindyknoch.com and newjerseyfrenchbulldogs.org, also share IP numbers with ridium.com.

Name Servers

ridium.com is delegated to three name servers: ns1.mdnsservice.com, ns2.mdnsservice.com and ns3.mdnsservice.com.

ridium.com has at least partial name server overlap with other domains, such as england.tc, kabat.com, taylor.biz and two others.

It is common to see these name servers used together with name servers ns1.mailbank.com and ns2.mailbank.com.

ns1.mdnsservice.com, ns2.mdnsservice.com and ns3.mdnsservice.com each resolve to two IP addresses: ns1.mdnsservice.com resolves to 216.40.47.18 and 2604:4000:0:d:216:40:47:18; ns2.mdnsservice.com resolves to 64.98.148.11 and 2604:4000:2800:d:64:99:148:11; ns3.mdnsservice.com resolves to 64.99.96.34 and 2604:4000:0:d:64:99:96:34.

Mail Servers

The sole mail server for ridium.com is ridium-com.mail.protection.outlook.com.

With 8 IP addresses total, ridium-com.mail.protection.outlook.com resolves to 52.101.9.17, 52.101.10.2, 52.101.10.10 and 5 others.