`loganfebruary.com`

DNSSEC	⚠️ Not signed
A	45.60.96.58^{🇺🇸 IMPERVA45.60.96.0/24 ORIXCOM via EMIX}
A	107.154.146.58^{🇺🇸 IMPERVA107.154.146.0/24 ORIXCOM via EMIX}
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`mail.loganfebruary.com` ⭐
		A	216.172.168.108^{🇺🇸 ORACLE-OCI-31898216.172.168.0/23 Google}
			PTR	`cs357.bluehost.com`
TXT	`v=spf1 a mx ptr include:bluehost.com ?all`
SOA	`ns1.bluehost.com`root@cs357.bluehost.com 2025-07-03 #5

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

⚠️ On DNS blocklist: tif

Same first word

loganfebruary.com

DNS History

6 records (5 active, 1 former)

●NSns1.bluehost.com2018-01-22 → 2026-07-15 · 2 obs

● 2018-01-22 13:24:20
● 2026-07-15 16:48:20

●NSns2.bluehost.com2018-01-22 → 2026-07-15 · 2 obs

● 2018-01-22 13:24:20
● 2026-07-15 16:48:20

●MXmail.loganfebruary.com2018-01-22 → 2026-07-15 · 2 obs

● 2018-01-22 13:24:20
● 2026-07-15 16:48:20

●A107.154.146.582026-02-28 → 2026-07-15 · 3 obs

○ 2018-01-22 13:24:20
● 2026-02-28 00:09:02
● 2026-07-15 16:48:20

○A108.179.230.1772018-01-22 → 2018-01-22 · 3 obs

● 2018-01-22 13:24:20
○ 2026-02-28 00:09:02
○ 2026-07-15 16:48:20

●A45.60.96.582026-02-28 → 2026-07-15 · 3 obs

○ 2018-01-22 13:24:20
● 2026-02-28 00:09:02
● 2026-07-15 16:48:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
loganfebruary.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)

No DS record for loganfebruary.com (unsigned zone)

⏱️ Timing

Total: 282ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`107.154.146.58, 45.60.96.58`
NS	2	`ns1.bluehost.com, ns2.bluehost.com`
MX	1	`mail.loganfebruary.com (pri: 0)`
TXT	1	`v=spf1 a mx ptr include:bluehost.com ?al`
SOA	1	`ns1.bluehost.com root.cs357.bluehost.com`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

loganfebruary.com directs to two IP numbers, 45.60.96.58 and 107.154.146.58

easyepublish.com, ei2aei8.sitelockcdn.net, 5mxuozx.sitelockcdn.net plus two other host names have IP numbers in common with loganfebruary.com.

Name Servers

Two name servers handle the delegation for loganfebruary.com: ns1.bluehost.com and ns2.bluehost.com.

The name server configuration of loganfebruary.com is shared with other domains, for instance doctorgittens.com, purplev.com, cellfonia.com and two others.

loganfebruary.com is at least partially co-delegated on name servers with other domains, such as gvcmtgrockport.com.

ns1.bluehost.com resolves to 162.159.24.80. ns2.bluehost.com resolves to 162.159.25.175. Both host names point to a single IP number.

Mail Servers

loganfebruary.com uses one mail server — mail.loganfebruary.com.

mail.loganfebruary.com carries a single IP number, which is 216.172.168.108.

loganfebruary.com - robtex.com