`dunkirk5.com`

DNSSEC	⚠️ Not signed
A	20.51.216.100^{🇺🇸 Microsoft20.48.0.0/12}
		PTR	`firehousesolutions.com`
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org`
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info`
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f27.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.27^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.26^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f26.1e100.net`
SOA	`ns1-03.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=1776001472

WOT: UNKNOWN (61/100)

Same first word

dunkirk5.com

DNS History

21 records (10 active, 11 former)

●NSns1-03.azure-dns.com2026-04-05 → 2026-04-12 · 3 obs

○ 2017-06-21 14:14:56
● 2026-04-05 10:45:08
● 2026-04-12 13:50:28

○NSns1.911hotdesigns.com2015-10-30 → 2016-02-05 · 5 obs

○ 2015-06-20 16:56:12
● 2015-10-30 20:38:18
● 2016-02-05 18:22:36
○ 2016-04-23 02:34:54
○ 2026-04-12 13:50:28

○NSns1.firecompanies.com2015-06-20 → 2015-06-20 · 3 obs

● 2015-06-20 16:56:12
○ 2015-10-30 20:38:18
○ 2026-04-12 13:50:28

○NSns1.hosting.com2016-04-23 → 2017-06-21 · 5 obs

○ 2016-02-05 18:22:36
● 2016-04-23 02:34:54
● 2017-06-21 14:14:56
○ 2026-04-05 10:45:08
○ 2026-04-12 13:50:28

●NSns2-03.azure-dns.net2026-04-05 → 2026-04-12 · 3 obs

○ 2017-06-21 14:14:56
● 2026-04-05 10:45:08
● 2026-04-12 13:50:28

○NSns2.911hotdesigns.com2015-10-30 → 2016-02-05 · 5 obs

○ 2015-06-20 16:56:12
● 2015-10-30 20:38:18
● 2016-02-05 18:22:36
○ 2016-04-23 02:34:54
○ 2026-04-12 13:50:28

○NSns2.firecompanies.com2015-06-20 → 2015-06-20 · 3 obs

● 2015-06-20 16:56:12
○ 2015-10-30 20:38:18
○ 2026-04-12 13:50:28

○NSns2.hosting.com2016-04-23 → 2017-06-21 · 5 obs

○ 2016-02-05 18:22:36
● 2016-04-23 02:34:54
● 2017-06-21 14:14:56
○ 2026-04-05 10:45:08
○ 2026-04-12 13:50:28

●NSns3-03.azure-dns.org2026-04-05 → 2026-04-12 · 3 obs

○ 2017-06-21 14:14:56
● 2026-04-05 10:45:08
● 2026-04-12 13:50:28

○NSns3.hosting.com2016-04-23 → 2017-06-21 · 5 obs

○ 2016-02-05 18:22:36
● 2016-04-23 02:34:54
● 2017-06-21 14:14:56
○ 2026-04-05 10:45:08
○ 2026-04-12 13:50:28

●NSns4-03.azure-dns.info2026-04-05 → 2026-04-12 · 3 obs

○ 2017-06-21 14:14:56
● 2026-04-05 10:45:08
● 2026-04-12 13:50:28

●MXalt1.aspmx.l.google.com2016-04-23 → 2026-04-12 · 3 obs

○ 2015-06-20 16:56:12
● 2016-04-23 02:34:54
● 2026-04-12 13:50:28

●MXalt2.aspmx.l.google.com2016-04-23 → 2026-04-12 · 3 obs

○ 2015-06-20 16:56:12
● 2016-04-23 02:34:54
● 2026-04-12 13:50:28

●MXalt3.aspmx.l.google.com2016-04-23 → 2026-04-12 · 3 obs

○ 2015-06-20 16:56:12
● 2016-04-23 02:34:54
● 2026-04-12 13:50:28

●MXalt4.aspmx.l.google.com2016-04-23 → 2026-04-12 · 3 obs

○ 2015-06-20 16:56:12
● 2016-04-23 02:34:54
● 2026-04-12 13:50:28

●MXaspmx.l.google.com2015-06-20 → 2026-04-12 · 2 obs

● 2015-06-20 16:56:12
● 2026-04-12 13:50:28

●A20.51.216.1002026-04-05 → 2026-04-12 · 3 obs

○ 2017-06-21 14:14:56
● 2026-04-05 10:45:08
● 2026-04-12 13:50:28

○A65.36.166.2402015-06-20 → 2015-06-20 · 3 obs

● 2015-06-20 16:56:12
○ 2015-10-30 20:38:18
○ 2026-04-12 13:50:28

○A69.167.152.42015-10-30 → 2016-02-05 · 5 obs

○ 2015-06-20 16:56:12
● 2015-10-30 20:38:18
● 2016-02-05 18:22:36
○ 2016-04-23 02:34:54
○ 2026-04-12 13:50:28

○A76.12.100.1472017-06-21 → 2017-06-21 · 4 obs

○ 2016-11-22 19:14:08
● 2017-06-21 14:14:56
○ 2026-04-05 10:45:08
○ 2026-04-12 13:50:28

○A76.12.100.1482016-04-23 → 2016-11-22 · 5 obs

○ 2016-02-05 18:22:36
● 2016-04-23 02:34:54
● 2016-11-22 19:14:08
○ 2017-06-21 14:14:56
○ 2026-04-12 13:50:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
dunkirk5.com	ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.3

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dunkirk5.com (unsigned zone)

⏱️ Timing

Total: 165ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.51.216.100`
NS	4	`ns1-03.azure-dns.com, ns2-03.azure-dns.net...`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns1-03.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

dunkirk5.com points to IP number: 20.51.216.100.

Other host names such as kivfd.org, lineborovfd.org, cheltenhamfirecompany.org, sayvillefd.org and btvfd3.com share IPs with dunkirk5.com.

Name Servers

dunkirk5.com is delegated to four name servers: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.

dunkirk5.com at least partially shares name servers with other domains, for instance bingyahoonetwork.com.pe, porto.ms, game-play.com, fortalezamateriales.com and durr-france.com.

Host names with two IP numbers: ns1-03.azure-dns.com points to 2603:1061:0:700::3 and 13.107.236.3; ns4-03.azure-dns.info points to 2620:1ec:bda:700::3 and 208.84.5.3; ns2-03.azure-dns.net points to 2620:1ec:8ec:700::3 and 150.171.21.3; ns3-03.azure-dns.org points to 2a01:111:4000:700::3 and 204.14.183.3.

Mail Servers

Five mail servers handle dunkirk5.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

dunkirk5.com shares at least partially some mail servers with other domains, including keynshamelim.com, dextrade.com, coartha.com, imbl.dk and phorest.com.au.