freddry.com - dns.ninja

`freddry.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}
NS	`ns03.domaincontrol.com` ⭐
		A	2603:5:2150::2^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns03.domaincontrol.com`
		A	97.74.101.2^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns03.domaincontrol.com`
NS	`ns04.domaincontrol.com`
		A	2603:5:2250::2^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns04.domaincontrol.com`
		A	173.201.69.2^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns04.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
TXT	`_globalsign-domain-verification=siI-QZN6EXUe9aYRXdR9xSIPLf-1fYSxYl81ZPQABE`
TXT	`v=spf1 a mx ptr include:secureserver.net ~all`
SOA	`ns03.domaincontrol.com`dns@jomax.net 2025-01-02 #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=1783148361

Previously MX for

freddry.com

Same first word

freddry.com

DNS History

9 records (5 active, 4 former)

●NSns03.domaincontrol.com2026-02-18 → 2026-07-04 · 3 obs

○ 2017-02-02 15:13:26
● 2026-02-18 23:49:22
● 2026-07-04 07:15:30

●NSns04.domaincontrol.com2026-02-18 → 2026-07-04 · 3 obs

○ 2017-02-02 15:13:26
● 2026-02-18 23:49:22
● 2026-07-04 07:15:30

○NSns181.websitewelcome.com2015-08-15 → 2017-02-02 · 4 obs

● 2015-08-15 12:45:30
● 2017-02-02 15:13:26
○ 2026-02-18 23:49:22
○ 2026-07-04 07:15:30

○NSns182.websitewelcome.com2015-08-15 → 2017-02-02 · 4 obs

● 2015-08-15 12:45:30
● 2017-02-02 15:13:26
○ 2026-02-18 23:49:22
○ 2026-07-04 07:15:30

●MXaspmx.l.google.com2026-02-18 → 2026-07-04 · 3 obs

○ 2017-02-02 15:13:26
● 2026-02-18 23:49:22
● 2026-07-04 07:15:30

○MXfreddry.com2015-08-15 → 2017-02-02 · 4 obs

● 2015-08-15 12:45:30
● 2017-02-02 15:13:26
○ 2026-02-18 23:49:22
○ 2026-07-04 07:15:30

●A15.197.148.332026-02-18 → 2026-07-04 · 3 obs

○ 2017-02-02 15:13:26
● 2026-02-18 23:49:22
● 2026-07-04 07:15:30

○A192.185.102.2452015-08-15 → 2017-02-02 · 4 obs

● 2015-08-15 12:45:30
● 2017-02-02 15:13:26
○ 2026-02-18 23:49:22
○ 2026-07-04 07:15:30

●A3.33.130.1902026-02-18 → 2026-07-04 · 3 obs

○ 2017-02-02 15:13:26
● 2026-02-18 23:49:22
● 2026-07-04 07:15:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
freddry.com	ns03.domaincontrol.com, ns04.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.69.2

NS records: ns03.domaincontrol.com, ns04.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for freddry.com (unsigned zone)

⏱️ Timing

Total: 181ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns03.domaincontrol.com, ns04.domaincontrol.com`
MX	1	`aspmx.l.google.com (pri: 1)`
TXT	2	`_globalsign-domain-verification=siI-QZN6, v=spf1 a mx ptr include:secureserver.net`
SOA	1	`ns03.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns03.domaincontrol.com, ns03.domaincontrol.com, ns04.domaincontrol.com...)

Analysis

IP Addresses

freddry.com resolves to the IP addresses 3.33.130.190 and 15.197.148.33

Two other host names, along with rondesastre.com, doncoursey.com and saturnretreats.com, also share IP numbers with freddry.com.

Name Servers

freddry.com has two authoritative name servers — ns03.domaincontrol.com and ns04.domaincontrol.com.

freddry.com shares its NS records with other domains, for example coppercountryaa.com, camopal.com, teascloset.com and two others.

The name servers for freddry.com overlap at least partially with those of other domains — for example onthegoradio.com.

Both ns03.domaincontrol.com and ns04.domaincontrol.com have two IP addresses each. ns03.domaincontrol.com resolves to 97.74.101.2 and 2603:5:2150::2; ns04.domaincontrol.com resolves to 173.201.69.2 and 2603:5:2250::2.

Mail Servers

The sole mail server for freddry.com is aspmx.l.google.com.

Among the domains sharing a mail server setup with freddry.com are alduval.cl, swelldeal.com, fluwei.com and two others.

There is at least a partial MX overlap between freddry.com and other domains, including ns500758.ns500759.ns500759.ns500759.ns500736.ns500735.ns500698.ns500576.ns500576.ns500698.ns500698.ns500708.ns500619.ns500576.ns500619.ns500619.trackreceptor.com, ns500742.ns500731.ns500731.ns500754.ns500671.ns500742.ns500731.ns500731.ns500688.ns500678.ns500649.ns500678.ns500678.ns500671.lusty(0x736c7574)z.com, ns500759.ns500758.ns500759.ns500758.ns500758.ns500758.ns500698.ns500736.ns500698.ns500698.ns500735.ns500708.ns500619.ns500698.ns500576.ns500619.ns500576.trackreceptor.com and two others.

These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 5 others.

aspmx.l.google.com has two IP addresses: 64.233.180.27 and 2607:f8b0:4004:c1f::1a.