boingify.com - dns.ninja
boingify.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 35.232.9.23🇺🇸 Google35.232.0.0/16 | ||||||
| PTR | 23.9.232.35.bc.googleusercontent.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 | boingify.com ⭐ | ||||||
| A | 35.232.9.23🇺🇸 Google35.232.0.0/16 | ||||||
| PTR | 23.9.232.35.bc.googleusercontent.com | ||||||
| TXT | v=spf1 a mx ptr include:com ?all | ||||||
| SOA | ns1.bluehost.comdnsadmin@bluehost.com 2018-08-28 #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.netnstld@verisign-grs.com serial=1782859781 | ||||||
MX for
boingify.com |
Same first word
boingify.com |
Similar names
DNS History
5 records (4 active, 1 former)
●NSns1.bluehost.com2016-12-15 → 2026-06-30 · 2 obs
● 2026-06-30 22:55:42
●NSns2.bluehost.com2016-12-15 → 2026-06-30 · 2 obs
● 2026-06-30 22:55:42
●MXboingify.com2016-12-15 → 2026-06-30 · 2 obs
● 2026-06-30 22:55:42
○A104.197.103.1122016-12-15 → 2017-12-15 · 4 obs
● 2017-12-15 12:20:34
○ 2026-03-31 08:50:10
○ 2026-06-30 22:55:42
●A35.232.9.232026-03-31 → 2026-06-30 · 3 obs
● 2026-03-31 08:50:10
● 2026-06-30 22:55:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| boingify.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 boingify.com (unsigned zone)
⏱️ Timing
Total: 219ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 35.232.9.23 |
| NS | 2 | ns2.bluehost.com, ns1.bluehost.com |
| MX | 1 | boingify.com (pri: 0) |
| TXT | 1 | v=spf1 a mx ptr include:com ?all |
| SOA | 1 | ns1.bluehost.com dnsadmin.bluehost.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)
Analysis
Mail Server Role
boingify.com handles its own mail, functioning as its own mail server.
IP Addresses
boingify.com resolves to just one IP address, 35.232.9.23.
Name Servers
boingify.com is delegated to two name servers: ns1.bluehost.com and ns2.bluehost.com.
boingify.com shares its NS records with other domains, for example mypestex.com, independentbaseball.net, vegetarianstar.com and two others.
boingify.com and other domains like losangeleseducationlawyer.com, hrrh.com and theelephantcamp.com share some name servers
ns1.bluehost.com → 162.159.24.80 and ns2.bluehost.com → 162.159.25.175: one IP number per host name.
Mail Servers
boingify.com is served by just one mail server: boingify.com.
boingify.com resolves to a single IP number: 35.232.9.23.