optimizingfi.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`optimizingfi.com`

DNSSEC	⚠️ Not signed
A	162.241.252.236
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4013:c14::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`eb-in-f27.1e100.net`
		A	142.251.31.26^{🇺🇸 Google142.251.31.0/24}
			PTR	`eq-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:4403::1b^{🇮🇪 Google2a00:1450:4025::/48}
			PTR	`yuskelf-in-f27.1e100.net`
		A	192.178.228.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`yuskelf-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4025:c01::1b^{🇵🇱 Google2a00:1450:4025::/48}
			PTR	`rd-in-f27.1e100.net`
		A	142.250.147.26^{🇺🇸 Google142.250.147.0/24}
			PTR	`rd-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4010:c22::1b^{🇫🇮 Google2a00:1450:4010::/48}
			PTR	`yulpptr-in-f27.1e100.net`
		A	172.253.152.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yulpptr-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2404:6800:4000:1027::1b^{🇮🇳 Google2404:6800::/32}
			PTR	`ncboms-in-f27.1e100.net`
		A	192.179.20.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncboms-in-f26.1e100.net`
TXT	`google-site-verification=nHNOdKpgm1PGhlPvHTLplzKtc6pY3Hu7y5KVOTsG-58`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.bluehost.com`root@box5749.bluehost.com 2026-08-06 #1

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

Same first word

optimizingfi.com

DNS History

9 records (8 active, 1 former)

●NSns1.bluehost.com2020-02-06 → 2026-10-23 · 2 obs

● 2020-02-06 01:15:58
● 2026-10-23 02:14:02

●NSns2.bluehost.com2020-02-06 → 2026-10-23 · 2 obs

● 2020-02-06 01:15:58
● 2026-10-23 02:14:02

●MXalt1.aspmx.l.google.com2026-08-18 → 2026-10-23 · 3 obs

○ 2020-02-06 01:15:58
● 2026-08-18 21:38:52
● 2026-10-23 02:14:02

●MXalt2.aspmx.l.google.com2026-08-18 → 2026-10-23 · 3 obs

○ 2020-02-06 01:15:58
● 2026-08-18 21:38:52
● 2026-10-23 02:14:02

●MXalt3.aspmx.l.google.com2026-08-18 → 2026-10-23 · 3 obs

○ 2020-02-06 01:15:58
● 2026-08-18 21:38:52
● 2026-10-23 02:14:02

●MXalt4.aspmx.l.google.com2026-08-18 → 2026-10-23 · 3 obs

○ 2020-02-06 01:15:58
● 2026-08-18 21:38:52
● 2026-10-23 02:14:02

●MXaspmx.l.google.com2026-08-18 → 2026-10-23 · 3 obs

○ 2020-02-06 01:15:58
● 2026-08-18 21:38:52
● 2026-10-23 02:14:02

○MXmail.optimizingfi.com2020-02-06 → 2020-02-06 · 3 obs

● 2020-02-06 01:15:58
○ 2026-08-18 21:38:52
○ 2026-10-23 02:14:02

●A162.241.252.2362020-02-06 → 2026-10-23 · 2 obs

● 2020-02-06 01:15:58
● 2026-10-23 02:14:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, f.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net...	-
optimizingfi.com	ns1.bluehost.com, ns2.bluehost.com	2 records

✅ Authoritative Response

Server:162.159.24.80

NS records: ns1.bluehost.com, ns2.bluehost.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 502ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.252.236`
NS	2	`ns1.bluehost.com, ns2.bluehost.com`
MX	5	`alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`v=spf1 include:_spf.google.com ~all, google-site-verification=nHNOdKpgm1PGhlP`
SOA	1	`ns1.bluehost.com root.box5749.bluehost.c`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)

Analysis

IP Addresses

optimizingfi.com resolves to just one IP address, 162.241.252.236.

Name Servers

optimizingfi.com is served by two delegated name servers, ns1.bluehost.com and ns2.bluehost.com.

ns1.bluehost.com and ns2.bluehost.com each resolve to one IP number: ns1.bluehost.com points to 162.159.24.80 and ns2.bluehost.com points to 162.159.25.175.

Mail Servers

optimizingfi.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

Host names that have two IP addresses:

aspmx.l.google.com maps to two IP addresses — 142.251.31.26 and 2a00:1450:4013:c14::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.228.27 and 2a00:1450:4025:4403::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 142.250.147.26 and 2a00:1450:4025:c01::1b.

alt3.aspmx.l.google.com maps to two IP addresses — 172.253.152.27 and 2a00:1450:4010:c22::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 192.179.20.26 and 2404:6800:4000:1027::1b.