`britaintourism.com`

DNSSEC	⚠️ Not signed
A	20.106.184.214^{🇺🇸 Microsoft20.64.0.0/10}
NS	`ns27.domaincontrol.com` ⭐
		A	2603:5:2171::e^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns27.domaincontrol.com`
		A	97.74.103.14^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns27.domaincontrol.com`
NS	`ns28.domaincontrol.com`
		A	2603:5:2271::e^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns28.domaincontrol.com`
		A	173.201.71.14^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns28.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f26.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.26^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f26.1e100.net`
		A	172.253.145.26^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f26.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	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.26^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f26.1e100.net`
SOA	`ns27.domaincontrol.com`dns@jomax.net 2023-05-25 #8

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

Same first word

britaintourism.com

DNS History

18 records (8 active, 10 former)

○NSdns1.name-services.com2015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

○NSdns2.name-services.com2015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

○NSdns3.name-services.com2015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

○NSdns4.name-services.com2015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

○NSdns5.name-services.com2015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

○NSns1.uniregistrymarket.link2017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-25 16:06:54
● 2017-08-17 01:36:20
○ 2026-03-30 19:08:30
○ 2026-04-25 17:47:08

○NSns2.uniregistrymarket.link2017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-25 16:06:54
● 2017-08-17 01:36:20
○ 2026-03-30 19:08:30
○ 2026-04-25 17:47:08

●NSns27.domaincontrol.com2026-03-30 → 2026-04-25 · 3 obs

○ 2017-08-17 01:36:20
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●NSns28.domaincontrol.com2026-03-30 → 2026-04-25 · 3 obs

○ 2017-08-17 01:36:20
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●MXalt1.aspmx.l.google.com2026-03-30 → 2026-04-25 · 3 obs

○ 2016-11-25 16:06:54
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●MXalt2.aspmx.l.google.com2026-03-30 → 2026-04-25 · 3 obs

○ 2016-11-25 16:06:54
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●MXalt3.aspmx.l.google.com2026-03-30 → 2026-04-25 · 3 obs

○ 2016-11-25 16:06:54
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●MXalt4.aspmx.l.google.com2026-03-30 → 2026-04-25 · 3 obs

○ 2016-11-25 16:06:54
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

●MXaspmx.l.google.com2026-03-30 → 2026-04-25 · 3 obs

○ 2016-11-25 16:06:54
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

○MXp.nsm.ctmail.com2015-07-31 → 2016-03-22 · 4 obs

● 2015-07-31 22:15:46
● 2016-03-22 06:21:26
○ 2016-11-25 16:06:54
○ 2026-04-25 17:47:08

●A20.106.184.2142026-03-30 → 2026-04-25 · 3 obs

○ 2017-08-17 01:36:20
● 2026-03-30 19:08:30
● 2026-04-25 17:47:08

○A69.172.201.1532017-08-17 → 2017-08-17 · 4 obs

○ 2016-11-25 16:06:54
● 2017-08-17 01:36:20
○ 2026-03-30 19:08:30
○ 2026-04-25 17:47:08

○A69.64.147.2432015-07-31 → 2016-11-25 · 4 obs

● 2015-07-31 22:15:46
● 2016-11-25 16:06:54
○ 2017-08-17 01:36:20
○ 2026-04-25 17:47:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
britaintourism.com	ns27.domaincontrol.com, ns28.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.71.14

NS records: ns27.domaincontrol.com, ns28.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for britaintourism.com (unsigned zone)

⏱️ Timing

Total: 162ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.106.184.214`
NS	2	`ns27.domaincontrol.com, ns28.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
SOA	1	`ns27.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns27.domaincontrol.com, ns27.domaincontrol.com, ns28.domaincontrol.com...)

Analysis

IP Addresses

britaintourism.com resolves to a single IP address: 20.106.184.214.

Other host names including topsailist.com, southerneuropeantourism.com, gatourism.com, xiamentourism.com and worldtourism.net share IP numbers with britaintourism.com.

Name Servers

britaintourism.com's delegation uses two name servers, ns27.domaincontrol.com and ns28.domaincontrol.com.

britaintourism.com shares the same name server setup as other domains, for example odeki.at, grandmagorgeous.com, xplus.tv, smartii.com and stuffnsuch.com.