secure-reg.com - dns.ninja

`secure-reg.com`

DNSSEC	⚠️ Not signed
NS	`ns1-05.azure-dns.com` ⭐
		A	2603:1061:0:700::5^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
		A	13.107.236.5^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
NS	`ns2-05.azure-dns.net`
		A	2620:1ec:8ec:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
		A	150.171.21.5^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
NS	`ns3-05.azure-dns.org`
		A	2a01:111:4000:700::5^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-05.azure-dns.org`
		A	204.14.183.5^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-05.azure-dns.org`
NS	`ns4-05.azure-dns.info`
		A	2620:1ec:bda:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
		A	208.84.5.5^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
MX	`securereg-com01e.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::14^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00307.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00201.inbound.protection.outlook.com`
		A	52.101.8.51^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm1pr04cu00203.inbound.protection.outlook.com`
		A	52.101.10.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00106.inbound.protection.outlook.com`
		A	52.101.41.28^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	52.101.41.56^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr21cu00100.inbound.protection.outlook.com`
TXT	`MS=ms82485199`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-05.azure-dns.com`azuredns-hostmaster@microsoft.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=1785897839

⚠️ On DNS blocklist: tif

Same first word

secure-reg.com

secure-reg.net

DNS History

10 records (5 active, 5 former)

●NSns1-05.azure-dns.com2026-02-26 → 2026-08-05 · 3 obs

○ 2017-04-05 23:41:48
● 2026-02-26 05:21:16
● 2026-08-05 03:05:12

●NSns2-05.azure-dns.net2026-02-26 → 2026-08-05 · 3 obs

○ 2017-04-05 23:41:48
● 2026-02-26 05:21:16
● 2026-08-05 03:05:12

●NSns3-05.azure-dns.org2026-02-26 → 2026-08-05 · 3 obs

○ 2017-04-05 23:41:48
● 2026-02-26 05:21:16
● 2026-08-05 03:05:12

●NSns4-05.azure-dns.info2026-02-26 → 2026-08-05 · 3 obs

○ 2017-04-05 23:41:48
● 2026-02-26 05:21:16
● 2026-08-05 03:05:12

○NSns51.domaincontrol.com2015-05-24 → 2017-04-05 · 4 obs

● 2015-05-24 01:59:58
● 2017-04-05 23:41:48
○ 2026-02-26 05:21:16
○ 2026-08-05 03:05:12

○NSns52.domaincontrol.com2015-05-24 → 2017-04-05 · 4 obs

● 2015-05-24 01:59:58
● 2017-04-05 23:41:48
○ 2026-02-26 05:21:16
○ 2026-08-05 03:05:12

○MXmailstore1.secureserver.net2015-05-24 → 2017-04-05 · 4 obs

● 2015-05-24 01:59:58
● 2017-04-05 23:41:48
○ 2026-02-26 05:21:16
○ 2026-08-05 03:05:12

●MXsecurereg-com01e.mail.protection.outlook.com2026-02-26 → 2026-08-05 · 3 obs

○ 2017-04-05 23:41:48
● 2026-02-26 05:21:16
● 2026-08-05 03:05:12

○MXsmtp.secureserver.net2015-05-24 → 2017-04-05 · 4 obs

● 2015-05-24 01:59:58
● 2017-04-05 23:41:48
○ 2026-02-26 05:21:16
○ 2026-08-05 03:05:12

○A50.63.202.432015-05-24 → 2017-04-05 · 4 obs

● 2015-05-24 01:59:58
● 2017-04-05 23:41:48
○ 2026-02-26 05:21:16
○ 2026-08-05 03:05:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
secure-reg.com	ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.5

NS records: ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for secure-reg.com (unsigned zone)

⏱️ Timing

Total: 319ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
MX	1	`securereg-com01e.mail.protection.outlook`
TXT	2	`MS=ms82485199, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1-05.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-05.azure-dns.com, ns1-05.azure-dns.com)

Analysis

Name Servers

The domain secure-reg.com is delegated to these four name servers: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

secure-reg.com has at least partial name server overlap with other domains, such as xboxone.fr, msi5.com, omega-swatch.com and two others.

ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org all point to exactly two IP numbers each: ns1-05.azure-dns.com → 13.107.236.5 and 2603:1061:0:700::5; ns4-05.azure-dns.info → 208.84.5.5 and 2620:1ec:bda:700::5; ns2-05.azure-dns.net → 150.171.21.5 and 2620:1ec:8ec:700::5; ns3-05.azure-dns.org → 204.14.183.5 and 2a01:111:4000:700::5.

Mail Servers

secure-reg.com routes its mail through a single mail server, securereg-com01e.mail.protection.outlook.com.

securereg-com01e.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.8.51, 52.101.10.6 and 52.101.41.28, along with 5 other.