`crownscheduling.com`

DNSSEC	⚠️ Not signed
A	13.223.239.126^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
		PTR	`ec2-13-223-239-126.compute-1.amazonaws.com`
A	100.52.151.5^{🇺🇸 Amazon100.48.0.0/12 EC2 IAD prefix}
NS	`ns-853.awsdns-42.net` ⭐
		A	2600:9000:5303:5500::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-853.awsdns-42.net`
		A	205.251.195.85^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-853.awsdns-42.net`
NS	`ns-1319.awsdns-36.org`
		A	2600:9000:5305:2700::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1319.awsdns-36.org`
		A	205.251.197.39^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1319.awsdns-36.org`
NS	`ns-1650.awsdns-14.co.uk`
		A	2600:9000:5306:7200::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1650.awsdns-14.co.uk`
		A	205.251.198.114^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1650.awsdns-14.co.uk`
NS	`ns-33.awsdns-04.com`
		A	2600:9000:5300:2100::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-33.awsdns-04.com`
		A	205.251.192.33^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-33.awsdns-04.com`
MX	`inbound-smtp.us-east-1.amazonaws.com` ⭐
		A	3.211.210.226^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-211-210-226.compute-1.amazonaws.com`
		A	44.206.9.87^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-206-9-87.compute-1.amazonaws.com`
		A	44.210.166.32^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-210-166-32.compute-1.amazonaws.com`
		A	54.164.173.191^{🇺🇸 Amazon54.164.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-164-173-191.compute-1.amazonaws.com`
		A	54.197.5.236^{🇺🇸 Amazon54.196.0.0/15 EC2 IAD 54.196.0.0/15}
			PTR	`ec2-54-197-5-236.compute-1.amazonaws.com`
SOA	`ns-853.awsdns-42.net`awsdns-hostmaster@amazon.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=1776176232

Same first word

crownscheduling.com

DNS History

18 records (7 active, 11 former)

●NSns-1319.awsdns-36.org2026-03-17 → 2026-04-14 · 3 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
● 2026-04-14 14:35:24

●NSns-1650.awsdns-14.co.uk2026-03-17 → 2026-04-14 · 3 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
● 2026-04-14 14:35:24

●NSns-33.awsdns-04.com2026-03-17 → 2026-04-14 · 3 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
● 2026-04-14 14:35:24

●NSns-853.awsdns-42.net2026-03-17 → 2026-04-14 · 3 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
● 2026-04-14 14:35:24

○NSns1.everleap.com2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 05:05:50
○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

○NSns2.everleap.com2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 05:05:50
○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

○NSns3.everleap.com2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 05:05:50
○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

●MXinbound-smtp.us-east-1.amazonaws.com2026-03-17 → 2026-04-14 · 3 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
● 2026-04-14 14:35:24

○MXsm14.internetmailserver.net2016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 05:05:50
○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

●A100.52.151.52026-04-14 → 2026-04-14 · 3 obs

○ 2026-03-25 02:54:00
● 2026-04-14 14:35:20
● 2026-04-14 14:35:24

○A13.222.66.1802026-03-17 → 2026-03-17 · 4 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
○ 2026-03-25 02:54:00
○ 2026-04-14 14:35:24

●A13.223.239.1262026-04-14 → 2026-04-14 · 3 obs

○ 2026-03-25 02:54:00
● 2026-04-14 14:35:20
● 2026-04-14 14:35:24

○A199.233.255.822016-12-19 → 2016-12-19 · 3 obs

● 2016-12-19 05:05:50
○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

○A3.225.242.1842026-03-17 → 2026-04-14 · 2 obs

○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

○A44.199.78.1872026-03-17 → 2026-04-14 · 2 obs

○ 2026-03-17 18:27:34
○ 2026-04-14 14:35:24

○A52.23.53.2492026-03-17 → 2026-03-17 · 4 obs

○ 2016-12-19 05:05:50
● 2026-03-17 18:27:34
○ 2026-03-25 02:54:00
○ 2026-04-14 14:35:24

○A54.146.186.1572026-03-25 → 2026-03-25 · 4 obs

○ 2026-03-17 18:27:34
● 2026-03-25 02:54:00
○ 2026-04-14 14:35:20
○ 2026-04-14 14:35:24

○A98.83.103.1362026-03-25 → 2026-03-25 · 4 obs

○ 2026-03-17 18:27:34
● 2026-03-25 02:54:00
○ 2026-04-14 14:35:20
○ 2026-04-14 14:35:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
crownscheduling.com	ns-33.awsdns-04.com, ns-853.awsdns-42.net, ns-1650.awsdns-14.co.uk, ns-1319.awsdns-36.org	1 record

✅ Authoritative Response

Server:205.251.195.85

NS records: ns-33.awsdns-04.com, ns-853.awsdns-42.net, ns-1650.awsdns-14.co.uk, ns-1319.awsdns-36.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crownscheduling.com (unsigned zone)

⏱️ Timing

Total: 377ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.223.239.126, 100.52.151.5`
NS	4	`ns-1319.awsdns-36.org, ns-1650.awsdns-14.co.uk...`
MX	1	`inbound-smtp.us-east-1.amazonaws.com (pr`
SOA	1	`ns-853.awsdns-42.net awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-33.awsdns-04.com)

Analysis

IP Addresses

crownscheduling.com points to two IP numbers: 13.223.239.126 and 100.52.151.5.

Other host names, for instance ec2-13-223-239-126.compute-1.amazonaws.com, share IP numbers with crownscheduling.com.

Name Servers

crownscheduling.com is delegated to four name servers: ns-33.awsdns-04.com, ns-853.awsdns-42.net, ns-1319.awsdns-36.org and ns-1650.awsdns-14.co.uk.

crownscheduling.com at least partially shares name servers with other domains, for instance piedpiper.com.au, dispatchplus-nonprod.navblue.cloud, settlementadvantage.com, www.hospitalinfantilsaocamilo.com.br and site-visor.com.

Host names with two IP numbers:

ns-33.awsdns-04.com points to: 2600:9000:5300:2100::1 and 205.251.192.33.

ns-853.awsdns-42.net points to: 2600:9000:5303:5500::1 and 205.251.195.85.

ns-1319.awsdns-36.org points to: 2600:9000:5305:2700::1 and 205.251.197.39.

ns-1650.awsdns-14.co.uk points to: 2600:9000:5306:7200::1 and 205.251.198.114.

Mail Servers

crownscheduling.com is handled by a single mail server, inbound-smtp.us-east-1.amazonaws.com.

crownscheduling.com uses the same mail server configuration as other domains, such as wibond.awsapps.com, llsapps.org, statweb.site-ym.com, rnabiologylaboratory.slack.com and monashdancesport.slack.com.

crownscheduling.com shares mail servers with other domains at least in part, for instance coonsult.atlassian.net, knetikcloud.com, chantwest.atlassian.net, i-sight.atlassian.net and ncchca.org.

These mail servers are often used together with the mail servers inbound-smtp.us-west-2.amazonaws.com.

Host inbound-smtp.us-east-1.amazonaws.com points to five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32, 54.164.173.191 and 54.197.5.236.

crownscheduling.com - robtex.com