`djangobyexample.com`

DNSSEC	⚠️ Not signed
A	3.33.193.101^{🇺🇸 Amazon3.33.192.0/20}
		PTR	`a45ad4a8ca0ec4d65.awsglobalaccelerator.com`
A	15.197.246.237^{🇺🇸 Amazon15.197.240.0/20}
A	52.223.46.195^{🇺🇸 Amazon52.223.32.0/20}
A	99.83.183.127^{🇺🇸 Amazon99.83.176.0/20}
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
MX	`mx1.mailchannels.net` ⭐
		A	52.38.143.159^{🇺🇸 Amazon52.36.0.0/14 EC2 PDX prefix}
			PTR	`ec2-52-38-143-159.us-west-2.compute.amazonaws.com`
MX	`mx2.mailchannels.net` ⭐
		A	18.236.29.166^{🇺🇸 Amazon18.236.0.0/15 EC2 PDX prefix}
			PTR	`ec2-18-236-29-166.us-west-2.compute.amazonaws.com`
TXT	`v=spf1 include:amazonses.com ~all`
TXT	`openai-domain-verification=dv-DeUYPn4NQgEqkHXCtfmAfTFE`
SOA	`dns1.name-services.com`info@name-services.com serial=1706812981

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

Same first word

djangobyexample.com

DNS History

12 records (11 active, 1 former)

●NSdns1.name-services.com2015-08-10 → 2026-03-25 · 2 obs

● 2015-08-10 09:41:50
● 2026-03-25 04:09:50

●NSdns2.name-services.com2015-08-10 → 2026-03-25 · 2 obs

● 2015-08-10 09:41:50
● 2026-03-25 04:09:50

●NSdns3.name-services.com2015-08-10 → 2026-03-25 · 2 obs

● 2015-08-10 09:41:50
● 2026-03-25 04:09:50

●NSdns4.name-services.com2015-08-10 → 2026-03-25 · 2 obs

● 2015-08-10 09:41:50
● 2026-03-25 04:09:50

●NSdns5.name-services.com2015-08-10 → 2026-03-25 · 2 obs

● 2015-08-10 09:41:50
● 2026-03-25 04:09:50

●MXmx1.mailchannels.net2026-03-08 → 2026-03-25 · 2 obs

● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

●MXmx2.mailchannels.net2026-03-08 → 2026-03-25 · 2 obs

● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

●A15.197.246.2372026-03-08 → 2026-03-25 · 3 obs

○ 2017-03-26 08:18:36
● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

○A216.144.247.902015-08-10 → 2017-03-26 · 4 obs

● 2015-08-10 09:41:50
● 2017-03-26 08:18:36
○ 2026-03-08 23:02:10
○ 2026-03-25 04:09:50

●A3.33.193.1012026-03-08 → 2026-03-25 · 3 obs

○ 2017-03-26 08:18:36
● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

●A52.223.46.1952026-03-08 → 2026-03-25 · 3 obs

○ 2017-03-26 08:18:36
● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

●A99.83.183.1272026-03-08 → 2026-03-25 · 3 obs

○ 2017-03-26 08:18:36
● 2026-03-08 23:02:10
● 2026-03-25 04:09:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
djangobyexample.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.138

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for djangobyexample.com (unsigned zone)

⏱️ Timing

Total: 554ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`3.33.193.101, 52.223.46.195...`
NS	5	`dns1.name-services.com, dns4.name-services.com...`
MX	2	`mx2.mailchannels.net (pri: 0), mx1.mailchannels.net (pri: 0)`
TXT	2	`v=spf1 include:amazonses.com ~all, openai-domain-verification=dv-DeUYPn4NQg`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

IP Addresses

djangobyexample.com points to four IP numbers: 3.33.193.101, 15.197.246.237, 52.223.46.195 and 99.83.183.127.

Other host names, for instance spherical-alligator-8s34xyith8ou9lryra3zocr4.herokudns.com, profy.com.br, slidr.io, knowen.org and selmandesign.com share IP numbers with djangobyexample.com.

Name Servers

djangobyexample.com is delegated to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com and dns5.name-services.com.

djangobyexample.com at least partially shares name servers with other domains, for instance try-fortune.com, movie-downloads.com, u-sand.com, lvaragon.com and whitebeach.ca.