`hellofortbliss.com`

DNSSEC	⚠️ Not signed
A	173.201.96.1^{🇺🇸 GODADDY}
		PTR	`p3nlhg47c087.shr.prod.phx3.secureserver.net`
NS	`ns39.domaincontrol.com` ⭐
		A	2603:5:21d1::14^{🇺🇸 GODADDY-DNS}
			PTR	`ns39.domaincontrol.com`
		A	97.74.109.20^{🇺🇸 GODADDY-DNS}
			PTR	`ns39.domaincontrol.com`
NS	`ns40.domaincontrol.com`
		A	2603:5:22d1::14^{🇺🇸 GODADDY-DNS}
			PTR	`ns40.domaincontrol.com`
		A	173.201.77.20^{🇺🇸 GODADDY-DNS}
			PTR	`ns40.domaincontrol.com`
MX	`hellofortbliss-com.mail.protection.outlook.com` ⭐
TXT	`v=spf1 include:secureserver.net -all`
TXT	`NETORGFT15358415.onmicrosoft.com`
SOA	`ns39.domaincontrol.com`dns@jomax.net 2025-03-09 #0

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

Same first word

hellofortbliss.com

DNS History

6 records (4 active, 2 former)

●NSns39.domaincontrol.com2016-12-20 → 2026-02-23 · 2 obs

● 2016-12-20 21:17:42
● 2026-02-23 17:39:38

●NSns40.domaincontrol.com2016-12-20 → 2026-02-23 · 2 obs

● 2016-12-20 21:17:42
● 2026-02-23 17:39:38

●MXhellofortbliss-com.mail.protection.outlook.com2026-02-23 → 2026-02-23 · 3 obs

○ 2018-07-05 16:59:00
● 2026-02-23 17:39:36
● 2026-02-23 17:39:38

○MXmailstore1.secureserver.net2016-12-20 → 2018-07-05 · 4 obs

● 2016-12-20 21:17:42
● 2018-07-05 16:59:00
○ 2026-02-23 17:39:36
○ 2026-02-23 17:39:38

○MXsmtp.secureserver.net2016-12-20 → 2018-07-05 · 4 obs

● 2016-12-20 21:17:42
● 2018-07-05 16:59:00
○ 2026-02-23 17:39:36
○ 2026-02-23 17:39:38

●A173.201.96.12016-12-20 → 2026-02-23 · 2 obs

● 2016-12-20 21:17:42
● 2026-02-23 17:39:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net...	-
hellofortbliss.com	ns39.domaincontrol.com, ns40.domaincontrol.com	4 records

✅ Authoritative Response

Server: 97.74.109.20

NS records: ns39.domaincontrol.com, ns40.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for hellofortbliss.com (unsigned zone)

⏱️ Timing

Total: 261ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.201.96.1`
NS	2	`ns39.domaincontrol.com, ns40.domaincontrol.com`
MX	1	`hellofortbliss-com.mail.protection.outlo`
TXT	2	`v=spf1 include:secureserver.net -all, NETORGFT15358415.onmicrosoft.com`
SOA	1	`ns39.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns39.domaincontrol.com, ns39.domaincontrol.com, ns40.domaincontrol.com...)

AI analysis

hellofortbliss.com points to an IP address: 173.201.96.1.

other host names include 154st.com, srupal.com, lamorindabaseball.org, bosniana.com and rkottencpa.com; they share IP numbers with hellofortbliss.com.

Two name servers ns39.domaincontrol.com and ns40.domaincontrol.com handle the delegation for hellofortbliss.com.

hellofortbliss.com shares the same name server setup as other domains, for instance mccutcheon.co, twoparachutes.com, acmes.net, tarotan.com and decodeme.biz.

hellofortbliss.com shares name servers with other domains at least partially, for example royallogistics.net.

Host names with two IP numbers:

ns39.domaincontrol.com points to 2603:5:21d1::14 and 97.74.109.20.

ns40.domaincontrol.com points to 2603:5:22d1::14 and 173.201.77.20.

hellofortbliss.com is handled by a single mail server, hellofortbliss-com.mail.protection.outlook.com.

hellofortbliss.com - robtex.com