`kantaraccess.com`

DNSSEC	⚠️ Not signed
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
MX	`kantaraccess-com.mail.protection.outlook.com` ⭐
		A	52.101.68.8^{🇮🇪 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-du0pr03cu00100.inbound.protection.outlook.com`
		A	52.101.68.12^{🇮🇪 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-db9pr02cu00204.inbound.protection.outlook.com`
		A	52.101.73.1^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-am3pr04cu00501.inbound.protection.outlook.com`
		A	52.101.73.16^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-as2pr05cu00100.inbound.protection.outlook.com`
TXT	`MS=ms13539569`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`_9lethoa6stqqi9c63b06y2laiwey31f`
SOA	`ns1-01.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=1785644857

Same first word

kantaraccess.com

Similar names

saracenstack.click

arcanestacks.com

DNS History

12 records (5 active, 7 former)

●NSns1-01.azure-dns.com2026-02-23 → 2026-08-02 · 3 obs

○ 2017-09-20 07:38:26
● 2026-02-23 12:32:22
● 2026-08-02 04:46:44

○NSns1.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

●NSns2-01.azure-dns.net2026-02-23 → 2026-08-02 · 3 obs

○ 2017-09-20 07:38:26
● 2026-02-23 12:32:22
● 2026-08-02 04:46:44

○NSns2.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

●NSns3-01.azure-dns.org2026-02-23 → 2026-08-02 · 3 obs

○ 2017-09-20 07:38:26
● 2026-02-23 12:32:22
● 2026-08-02 04:46:44

●NSns4-01.azure-dns.info2026-02-23 → 2026-08-02 · 3 obs

○ 2017-09-20 07:38:26
● 2026-02-23 12:32:22
● 2026-08-02 04:46:44

○NSns5.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

○NSns6.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

●MXkantaraccess-com.mail.protection.outlook.com2026-02-23 → 2026-08-02 · 3 obs

○ 2017-09-20 07:38:26
● 2026-02-23 12:32:22
● 2026-08-02 04:46:44

○MXrelay1.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

○MXrelay2.netnames.net2016-12-15 → 2017-09-20 · 4 obs

● 2016-12-15 12:31:52
● 2017-09-20 07:38:26
○ 2026-02-23 12:32:22
○ 2026-08-02 04:46:44

○A185.26.230.1292016-12-15 → 2016-12-15 · 3 obs

● 2016-12-15 12:31:52
○ 2017-09-20 07:38:26
○ 2026-08-02 04:46:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net...	-
kantaraccess.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for kantaraccess.com (unsigned zone)

⏱️ Timing

Total: 284ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
MX	1	`kantaraccess-com.mail.protection.outlook`
TXT	3	`MS=ms13539569, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

Four name servers handle the delegation for kantaraccess.com: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

kantaraccess.com partially shares its NS delegation with several other domains, including weland.se, fpq.info, smirthwaite.com and two others.

ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org each carry two IP addresses. ns1-01.azure-dns.com has 13.107.236.1 and 2603:1061:0:700::1; ns4-01.azure-dns.info has 208.84.5.1 and 2620:1ec:bda:700::1; ns2-01.azure-dns.net has 150.171.21.1 and 2620:1ec:8ec:700::1; ns3-01.azure-dns.org has 204.14.183.1 and 2a01:111:4000:700::1.

Mail Servers

kantaraccess.com uses one mail server — kantaraccess-com.mail.protection.outlook.com.

kantaraccess-com.mail.protection.outlook.com points to four IP addresses: 52.101.68.8, 52.101.68.12, 52.101.73.1 and 52.101.73.16.

kantaraccess.com - robtex.com