whyfyle.com - dns.ninja

`whyfyle.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns01.domaincontrol.com` ⭐
		A	2603:5:2140::1^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns01.domaincontrol.com`
		A	97.74.100.1^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns01.domaincontrol.com`
NS	`ns02.domaincontrol.com`
		A	2603:5:2240::1^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns02.domaincontrol.com`
		A	173.201.68.1^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns02.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.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	2607:f8b0:4004:c19::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f26.1e100.net`
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.111.26^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f26.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 include:dc-aa8e722993._spfm.whyfyle.com ~all`
TXT	`google-site-verification=Gfo46sQTPPnyU0o_8xUnpIKn7T9puekvFjDyiq9WhYk`
SOA	`ns01.domaincontrol.com`dns@jomax.net 2026-07-17 #3

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

Same first word

whyfyle.com

DNS History

10 records (10 active, 0 former)

●NSns01.domaincontrol.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●NSns02.domaincontrol.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXalt1.aspmx.l.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXalt2.aspmx.l.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXalt3.aspmx.l.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXalt4.aspmx.l.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXaspmx.l.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●MXsmtp.google.com2026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●A15.197.225.1282026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

●A3.33.251.1682026-07-14 → 2026-07-31 · 2 obs

● 2026-07-14 13:36:46
● 2026-07-31 22:59:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net...	-
whyfyle.com	ns01.domaincontrol.com, ns02.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.68.1

NS records: ns01.domaincontrol.com, ns02.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whyfyle.com (unsigned zone)

⏱️ Timing

Total: 229ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns02.domaincontrol.com, ns01.domaincontrol.com`
MX	6	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	2	`v=spf1 include:dc-aa8e722993._spfm.whyfy, google-site-verification=Gfo46sQTPPnyU0o`
SOA	1	`ns01.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)

Analysis

IP Addresses

whyfyle.com points to the IP addresses 3.33.251.168 and 15.197.225.128

kylej.info, hokahey.agency, arabsea.us and two other host names share IP numbers with whyfyle.com.

Name Servers

whyfyle.com is served by two delegated name servers, ns01.domaincontrol.com and ns02.domaincontrol.com.

whyfyle.com uses the same name servers as several other domains — among them restopla.com, recoverybus.com, singlelengthgolfclubs.com and two more.

The DNS delegation for whyfyle.com at least partly coincides with that of other domains, investcorptages.it being one example.

Each of the two host names carries two IP addresses: ns01.domaincontrol.com points to 97.74.100.1 and 2603:5:2140::1, and ns02.domaincontrol.com points to 173.201.68.1 and 2603:5:2240::1.

Mail Servers

whyfyle.com uses 6 mail servers for delivery: smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

whyfyle.com has at least partial mail server overlap with other domains such as ns500765.ns500693.ns500693.ns500699.ns500734.ns500699.ns500588.ns500699.ns500683.ns500588.ns500612.ns500588.ns500602.ns500578.ns500110.dtrkdll.com, gvp.telefonica.com, datajournalist.dk and two more.

These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 4 others.

Hostnames that resolve to 9 IP addresses:

smtp.google.com carries IP addresses 142.251.16.26, 142.251.16.27 and 142.251.111.26, with 6 other addresses beyond those.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com maps to two IP addresses — 142.251.16.27 and 2607:f8b0:4004:c07::1a.

alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1a.

These two host names — smtp.google.com and aspmx.l.google.com — each point to 142.251.16.27 IP addresses.