sndbite.com - dns.ninja
sndbite.com
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=1785988304 | ||||||
Subdomains
mail.sndbite.com |
Same first word
sndbite.com |
Similar names
DNS History
9 records (7 active, 2 former)
●NSns1.bluehost.com2017-02-10 → 2026-08-06 · 2 obs
● 2026-08-06 04:18:12
●NSns2.bluehost.com2017-02-10 → 2026-08-06 · 2 obs
● 2026-08-06 04:18:12
●MXalt2.aspmx.l.google.com2026-05-12 → 2026-08-06 · 3 obs
● 2026-05-12 05:18:36
● 2026-08-06 04:18:12
●MXalt4.aspmx.l.google.com2026-05-12 → 2026-08-06 · 3 obs
● 2026-05-12 05:18:36
● 2026-08-06 04:18:12
●MXaspmx.l.google.com2026-05-12 → 2026-08-06 · 3 obs
● 2026-05-12 05:18:36
● 2026-08-06 04:18:12
○MXmail.sndbite.com2017-02-10 → 2017-02-10 · 3 obs
○ 2026-05-12 05:18:36
○ 2026-08-06 04:18:12
●A151.101.1.1952026-05-12 → 2026-08-06 · 3 obs
● 2026-05-12 05:18:36
● 2026-08-06 04:18:12
●A151.101.65.1952026-05-12 → 2026-08-06 · 3 obs
● 2026-05-12 05:18:36
● 2026-08-06 04:18:12
○A66.147.244.912017-02-10 → 2017-02-10 · 3 obs
○ 2026-05-12 05:18:36
○ 2026-08-06 04:18:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net... | - |
| sndbite.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 sndbite.com (unsigned zone)
⏱️ Timing
Total: 306ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 151.101.65.195, 151.101.1.195 |
| NS | 2 | ns2.bluehost.com, ns1.bluehost.com |
| MX | 3 | aspmx.l.google.com (pri: 1), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=7nYt-rDNjlhx5-h, v=spf1 ip4:50.87.253.50 a mx ptr include |
| SOA | 1 | ns1.bluehost.com root.box2161.bluehost.c |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.bluehost.com, ns2.bluehost.com)
Analysis
Hierarchy
sndbite.com is a parent domain of mail.sndbite.com.
IP Addresses
sndbite.com resolves to the IP addresses 151.101.1.195 and 151.101.65.195
modsaint.com, oakay.com, woosart.com and two other host names share IP numbers with sndbite.com.
Name Servers
sndbite.com is served by two delegated name servers, ns1.bluehost.com and ns2.bluehost.com.
sndbite.com uses the same name servers as several other domains — among them setamma.com, munepro.com, blawg401.com and two more.
The DNS delegation for sndbite.com at least partly coincides with that of other domains, vepamil.com.ec being one example.
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
sndbite.com is handled by three mail servers: aspmx.l.google.com, alt2.aspmx.l.google.com and alt4.aspmx.l.google.com.
sndbite.com has at least partial mail server overlap with other domains such as neth.net, ns500731.ns500754.ns500742.ns500671.ns500704.ns500704.ns500704.ns500678.ns500291.ns500678.ns500688.ns500671.ns500649.lustychickser.com, ns500693.ns500734.ns500693.ns500693.ns500693.ns500693.ns500699.ns500699.ns500683.ns500683.ns500588.ns500612.ns500588.ns500110.dtrkdll.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
aspmx.l.google.com resolves to 192.179.18.27 and 2607:f8b0:4004:c1b::1b. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a. alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b. All three hostnames point to two IP numbers each.