`white-force.com`

DNSSEC	⚠️ Not signed
A	134.209.149.205^{🇮🇳 DIGITALOCEAN134.209.144.0/20 DigitalOcean}
		PTR	`ubuntu-white-force-20.04`
NS	`ns1.digitalocean.com` ⭐
		A	2606:4700:52::ac40:34d2^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
		A	172.64.52.210^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.digitalocean.com`
NS	`ns2.digitalocean.com`
		A	2606:4700:5a::ac40:3515^{🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
		A	172.64.53.21^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.digitalocean.com`
NS	`ns3.digitalocean.com`
		A	2606:4700:52::ac40:31d1^{🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
		A	172.64.49.209^{🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns3.digitalocean.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c0b::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dd-in-f27.1e100.net`
		A	142.250.101.27^{🇺🇸 Google142.250.101.0/24}
			PTR	`dz-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:402::1a^{🇳🇱 Google2a00:1450:4025::/48}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.27^{🇺🇸 Google142.250.102.0/24}
			PTR	`rb-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f27.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	2a00:1450:4025:c01::1b^{🇵🇱 Google2a00:1450:4025::/48}
			PTR	`rd-in-f27.1e100.net`
		A	142.250.147.27^{🇺🇸 Google142.250.147.0/24}
			PTR	`rd-in-f27.1e100.net`
SOA	`ns1.digitalocean.com`hostmaster@white-force.com serial=1687893031

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

Same first word

white-force.com

DNS History

9 records (9 active, 0 former)

●NSns1.digitalocean.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●NSns2.digitalocean.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●NSns3.digitalocean.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●MXalt1.aspmx.l.google.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●MXalt2.aspmx.l.google.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●MXalt3.aspmx.l.google.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●MXalt4.aspmx.l.google.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●MXaspmx.l.google.com2026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

●A134.209.149.2052026-03-14 → 2026-03-25 · 2 obs

● 2026-03-14 05:29:42
● 2026-03-25 06:45:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net...	-
white-force.com	ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com	3 records

✅ Authoritative Response

Server:172.64.52.210

NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for white-force.com (unsigned zone)

⏱️ Timing

Total: 168ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`134.209.149.205`
NS	3	`ns1.digitalocean.com, ns2.digitalocean.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)...`
SOA	1	`ns1.digitalocean.com hostmaster.white-fo`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)

Analysis

IP Addresses

white-force.com resolves to a single IP: 134.209.149.205.

Name Servers

white-force.com delegates to three name servers: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

white-force.com shares some name servers with other domains, for example kemnet.ca, bartb.ie, 1.0.0.d.c.b.1.2.0.0.0.0.0.0.0.0.0.d.0.0.2.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa, campshankitunk.org and dealsandcouponsonline.com.

Host names with two IP numbers:

ns1.digitalocean.com: 2606:4700:52::ac40:34d2 and 172.64.52.210

ns2.digitalocean.com: 2606:4700:5a::ac40:3515 and 172.64.53.21

ns3.digitalocean.com: 2606:4700:52::ac40:31d1 and 172.64.49.209

Mail Servers

white-force.com is handled by five mail servers: 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.

white-force.com shares some mail servers with other domains, at least partially; for instance fccycleclub.org, aeronexus.co.za, r6two.com, meahana.io and aignermedia.de.