execscheduler.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`execscheduler.com`

DNSSEC	⚠️ Not signed
A	52.164.206.56^{🇮🇪 Microsoft52.160.0.0/11 MICROSOFT}
A	104.215.95.187^{🇺🇸 Microsoft104.208.0.0/13 MICROSOFT}
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
MX	`execscheduler-com.mail.protection.outlook.com` ⭐
TXT	`MS=ms29780465`
TXT	`MS=ms89705568`
TXT	`MS=ms40288384`
TXT	`MS=ms63783126`
TXT	`MS=ms44456025`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-04.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=1787351499

Same first word

execscheduler.com

Previous names

execsale.com

execsalesheadhunter.com

execsallied.com

execsanctuary.com

execsas.com

execsatlarge.com

execsavvy.com

execsb.com

execsbw.com

execsc.com

execscale.com

execscc.com

Next names

DNS History

13 records (7 active, 6 former)

●NSns1-04.azure-dns.com2026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○NSns1.msft.net2016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

●NSns2-04.azure-dns.net2026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○NSns2.msft.net2016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

●NSns3-04.azure-dns.org2026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○NSns3.msft.net2016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

●NSns4-04.azure-dns.info2026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○NSns4.msft.net2016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

●MXexecscheduler-com.mail.protection.outlook.com2016-12-20 → 2026-08-21 · 2 obs

● 2016-12-20 22:06:22
● 2026-08-21 22:55:50

●A104.215.95.1872026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○A40.84.199.2332016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

●A52.164.206.562026-02-28 → 2026-08-21 · 3 obs

○ 2018-01-13 12:25:36
● 2026-02-28 17:23:52
● 2026-08-21 22:55:50

○A52.178.167.1092016-12-20 → 2018-01-13 · 4 obs

● 2016-12-20 22:06:22
● 2018-01-13 12:25:36
○ 2026-02-28 17:23:52
○ 2026-08-21 22:55:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net...	-
execscheduler.com	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for execscheduler.com (unsigned zone)

⏱️ Timing

Total: 267ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.215.95.187, 52.164.206.56`
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
MX	1	`execscheduler-com.mail.protection.outloo`
TXT	6	`MS=ms29780465, MS=ms89705568...`
SOA	1	`ns1-04.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

execscheduler.com resolves to the IP addresses 52.164.206.56 and 104.215.95.187

msnservices.us, mcpvirtualbusinesscards.net, 70725-www.frxsoftware.com and two other host names share IP numbers with execscheduler.com.

Name Servers

The authoritative name servers for execscheduler.com are ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

execscheduler.com has at least partial name server overlap with other domains, such as sirvahomebenefits.com, panphobia.com, hotmail.live and two others.

ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org all point to exactly two IP numbers each: ns1-04.azure-dns.com → 13.107.236.4 and 2603:1061:0:700::4; ns4-04.azure-dns.info → 208.84.5.4 and 2620:1ec:bda:700::4; ns2-04.azure-dns.net → 150.171.21.4 and 2620:1ec:8ec:700::4; ns3-04.azure-dns.org → 204.14.183.4 and 2a01:111:4000:700::4.

Mail Servers

Mail for execscheduler.com is handled by a single mail server, execscheduler-com.mail.protection.outlook.com.