keysdfw.com - dns.ninja

`keysdfw.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
A	104.198.186.69^{🇺🇸 Google104.198.176.0/20}
NS	`ns25.domaincontrol.com` ⭐
		A	2603:5:2161::d^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns25.domaincontrol.com`
		A	97.74.102.13^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns25.domaincontrol.com`
NS	`ns26.domaincontrol.com`
		A	2603:5:2261::d^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns26.domaincontrol.com`
		A	173.201.70.13^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns26.domaincontrol.com`
MX	`keysecuritytx-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c803::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr21cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f90b::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00100.inbound.protection.outlook.com`
		A	52.101.8.42^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr03cu00402.inbound.protection.outlook.com`
		A	52.101.9.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00400.inbound.protection.outlook.com`
		A	52.101.10.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn8pr05cu00102.inbound.protection.outlook.com`
		A	52.101.11.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr03cu00102.inbound.protection.outlook.com`
TXT	`ppe-16cb34959ae11625177f`
TXT	`ppe-ea2e44035983dc844c51`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns25.domaincontrol.com`dns@jomax.net 2024-11-05 #21

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

Same first word

keysdfw.com

Similar names

yfdweks.top

DNS History

11 records (6 active, 5 former)

●NSns25.domaincontrol.com2026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21:08

●NSns26.domaincontrol.com2026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21:08

○NSns71.domaincontrol.com2016-12-20 → 2018-01-06 · 4 obs

● 2016-12-20 15:49:18
● 2018-01-06 08:57:00
○ 2026-03-18 05:29:02
○ 2026-08-07 23:21:08

○NSns72.domaincontrol.com2016-12-20 → 2018-01-06 · 4 obs

● 2016-12-20 15:49:18
● 2018-01-06 08:57:00
○ 2026-03-18 05:29:02
○ 2026-08-07 23:21:08

●MXkeysecuritytx-com.mail.protection.outlook.com2026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21:08

○MXmailstore1.secureserver.net2016-12-20 → 2018-01-06 · 4 obs

● 2016-12-20 15:49:18
● 2018-01-06 08:57:00
○ 2026-03-18 05:29:02
○ 2026-08-07 23:21:08

○MXsmtp.secureserver.net2016-12-20 → 2018-01-06 · 4 obs

● 2016-12-20 15:49:18
● 2018-01-06 08:57:00
○ 2026-03-18 05:29:02
○ 2026-08-07 23:21:08

●A104.198.186.692026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21:08

○A104.239.200.1552016-12-20 → 2018-01-06 · 4 obs

● 2016-12-20 15:49:18
● 2018-01-06 08:57:00
○ 2026-03-18 05:29:02
○ 2026-08-07 23:21:08

●A15.197.148.332026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21:08

●A3.33.130.1902026-03-18 → 2026-08-07 · 3 obs

○ 2018-01-06 08:57:00
● 2026-03-18 05:29:02
● 2026-08-07 23:21: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...	-
keysdfw.com	ns25.domaincontrol.com, ns26.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.102.13

NS records: ns25.domaincontrol.com, ns26.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for keysdfw.com (unsigned zone)

⏱️ Timing

Total: 154ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`3.33.130.190, 15.197.148.33...`
NS	2	`ns25.domaincontrol.com, ns26.domaincontrol.com`
MX	1	`keysecuritytx-com.mail.protection.outloo`
TXT	3	`ppe-16cb34959ae11625177f, ppe-ea2e44035983dc844c51...`
SOA	1	`ns25.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns25.domaincontrol.com, ns25.domaincontrol.com, ns26.domaincontrol.com...)

Analysis

IP Addresses

The hostname keysdfw.com resolves to three IP addresses: 3.33.130.190, 15.197.148.33 and 104.198.186.69.

spawith.us, topcup.net, fcestone.com plus two other host names have IP numbers in common with keysdfw.com.

Name Servers

keysdfw.com is delegated to two name servers: ns25.domaincontrol.com and ns26.domaincontrol.com.

The name server configuration of keysdfw.com is shared with other domains, for instance epetid.com, stephanosconstantinou.com, hightrailscyclery.com and two others.

keysdfw.com shares at least some of its name servers with other domains, such as alumail.it.

ns25.domaincontrol.com and ns26.domaincontrol.com each resolve to two IP addresses: ns25.domaincontrol.com points to 97.74.102.13 and 2603:5:2161::d, while ns26.domaincontrol.com points to 173.201.70.13 and 2603:5:2261::d.

Mail Servers

keysdfw.com uses one mail server — keysecuritytx-com.mail.protection.outlook.com.

keysdfw.com uses the same mail servers as other domains, including keysecuritytx.com.

keysecuritytx-com.mail.protection.outlook.com has 8 IP addresses: 52.101.8.42, 52.101.9.24, 52.101.10.10 plus 5 more.