whysosecure.com - dns.ninja

`whysosecure.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3032::6815:115a^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:af67^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.17.90^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.175.103^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ed.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b6f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c16f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ed.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:216f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ed.ns.cloudflare.com`
		A	108.162.193.111^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	172.64.33.111^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	173.245.59.111^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
NS	`lia.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ab9^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0b9^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lia.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20b9^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lia.ns.cloudflare.com`
		A	108.162.192.185^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	172.64.32.185^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
		A	173.245.58.185^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lia.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽¹¹⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁷³⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.17.90, 172.67.175.103
		IPv6 hints	2606:4700:3032::6815:115a, 2606:4700:3034::ac43:af67
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=35, name=cloudflare-ech.com
SOA	`ed.ns.cloudflare.com`dns@cloudflare.com serial=2409332376

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

Same first word

whysosecure.com

Similar names

whysocereus.com

DNS History

17 records (9 active, 8 former)

●NSed.ns.cloudflare.com2026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

●NSlia.ns.cloudflare.com2026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

○NSns1.bdm.microsoftonline.com2017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

○NSns2.bdm.microsoftonline.com2017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

○NSns3.bdm.microsoftonline.com2017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

○NSns4.bdm.microsoftonline.com2017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

●MXroute1.mx.cloudflare.net2026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

●MXroute2.mx.cloudflare.net2026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

●MXroute3.mx.cloudflare.net2026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

○MXwhysosecure-com.mail.protection.outlook.com2017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

●A104.21.17.902026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

●A172.67.175.1032026-02-18 → 2026-07-12 · 3 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
● 2026-07-12 11:23:48

○A198.57.213.1082017-05-11 → 2017-05-11 · 3 obs

● 2017-05-11 11:01:22
○ 2026-02-18 22:41:38
○ 2026-07-12 11:23:48

●A2606:4700:3032::6815:115a2026-07-11 → 2026-07-12 · 3 obs

○ 2026-02-18 22:41:38
● 2026-07-11 06:06:48
● 2026-07-12 11:23:48

○A2606:4700:3033::6815:115a2026-02-18 → 2026-02-18 · 4 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
○ 2026-07-11 06:06:48
○ 2026-07-12 11:23:48

●A2606:4700:3034::ac43:af672026-07-11 → 2026-07-12 · 3 obs

○ 2026-02-18 22:41:38
● 2026-07-11 06:06:48
● 2026-07-12 11:23:48

○A2606:4700:3036::ac43:af672026-02-18 → 2026-02-18 · 4 obs

○ 2017-05-11 11:01:22
● 2026-02-18 22:41:38
○ 2026-07-11 06:06:48
○ 2026-07-12 11:23:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
whysosecure.com	ed.ns.cloudflare.com, lia.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.185

NS records: ed.ns.cloudflare.com, lia.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 222ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.17.90, 172.67.175.103`
AAAA	2	`2606:4700:3034::ac43:af67, 2606:4700:3032::6815:115a`
NS	2	`ed.ns.cloudflare.com, lia.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 11), route2.mx.cloudflare.net (pri: 2)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ed.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (ed.ns.cloudflare.com, ed.ns.cloudflare.com, ed.ns.cloudflare.com...)

Analysis

IP Addresses

whysosecure.com resolves to four IP addresses: 104.21.17.90, 172.67.175.103, 2606:4700:3032::6815:115a and 2606:4700:3034::ac43:af67.

miarusso.xyz, izitrip.com, drainrod.com plus two other host names have IP numbers in common with whysosecure.com.

Name Servers

Two name servers handle the delegation for whysosecure.com: ed.ns.cloudflare.com and lia.ns.cloudflare.com.

The name server configuration of whysosecure.com is shared with other domains, for instance apotheken.center, wholefoods4healthyliving.com, sgfans.org and two others.

whysosecure.com partially shares its NS delegation with several other domains, including zhukel.ru, betaoutinnovations.net, lynnfield.co.uk and two others.

These name servers often co-occur with the name servers quentin.ns.cloudflare.com.

Hosts with 6 IP addresses each:

ed.ns.cloudflare.com resolves to 108.162.193.111, 172.64.33.111 and 173.245.59.111 among others, with 3 other IP addresses in total.

lia.ns.cloudflare.com resolves to 108.162.192.185, 172.64.32.185 and 173.245.58.185 among others, with 3 other IP addresses in total.

Mail Servers

whysosecure.com uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by whysosecure.com are shared with other domains: formaybelleza.com, tathwell.com, gcecosys.com and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.