firenance.com - dns.ninja
firenance.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 162.241.230.55🇺🇸 ORACLE-OCI-31898162.241.224.0/21 Google | ||||||
| PTR | box5150.bluehost.com | ||||||
| NS | ns1.bluehost.com ⭐ | ||||||
| A | 162.159.24.80Cloudflare162.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.175Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.bluehost.com | ||||||
| MX | mail.firenance.com ⭐ | ||||||
| A | 162.241.230.55🇺🇸 ORACLE-OCI-31898162.241.224.0/21 Google | ||||||
| PTR | box5150.bluehost.com | ||||||
| TXT | v=spf1 a mx include:websitewelcome.com ~all | ||||||
| SOA | NS1.BLUEHOST.comroot@BLUEHOST.com serial=124010408 | ||||||
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.netnstld@verisign-grs.com serial=1786334504 | ||||||
Subdomains
Same first word
firenance.com |
Similar names
DNS History
4 records (4 active, 0 former)
●NSns1.bluehost.com2017-11-15 → 2026-08-10 · 2 obs
● 2026-08-10 04:21:22
●NSns2.bluehost.com2017-11-15 → 2026-08-10 · 2 obs
● 2026-08-10 04:21:22
●MXmail.firenance.com2017-11-15 → 2026-08-10 · 2 obs
● 2026-08-10 04:21:22
●A162.241.230.552017-11-15 → 2026-08-10 · 2 obs
● 2026-08-10 04:21:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| firenance.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 firenance.com (unsigned zone)
⏱️ Timing
Total: 157ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.241.230.55 |
| NS | 2 | ns1.bluehost.com, ns2.bluehost.com |
| MX | 1 | mail.firenance.com (pri: 0) |
| TXT | 1 | v=spf1 a mx include:websitewelcome.com ~ |
| SOA | 1 | NS1.BLUEHOST.com root.BLUEHOST.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)
Analysis
Hierarchy
The parent domain of mail.firenance.com and www.firenance.com is firenance.com.
IP Addresses
firenance.com directs to one IP number, which is 162.241.230.55.
Among the host names that share IP numbers with firenance.com are rencartertucker.com, aliwalay.net, deblovesianlovesdeb.com and two others.
Name Servers
firenance.com uses two name servers for its delegation: ns1.bluehost.com and ns2.bluehost.com.
firenance.com has the same name server delegation as a number of other domains, such as horsetoheart.org, entraineurprivemontreal.com, theheartofgoldkennels.com and two more.
The name servers for firenance.com overlap at least in part with those of other domains, including injuryx.com and az.net.
Both ns1.bluehost.com and ns2.bluehost.com have a single IP address each — ns1.bluehost.com resolves to 162.159.24.80 while ns2.bluehost.com resolves to 162.159.25.175.
Mail Servers
firenance.com routes its mail through a single mail server, mail.firenance.com.
mail.firenance.com directs to just one IP number, 162.241.230.55.