bigdypper.com - dns.ninja
bigdypper.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=1786278049 | ||||||
Same first word
bigdypper.com |
DNS History
10 records (9 active, 1 former)
●NSns1.digitalocean.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●NSns2.digitalocean.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●NSns3.digitalocean.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●MXalt1.aspmx.l.google.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●MXalt2.aspmx.l.google.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●MXalt3.aspmx.l.google.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●MXalt4.aspmx.l.google.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
●MXaspmx.l.google.com2016-12-13 → 2026-08-09 · 2 obs
● 2026-08-09 12:26:46
○A104.131.165.2292016-12-13 → 2017-11-02 · 4 obs
● 2017-11-02 19:10:36
○ 2026-04-05 23:36:52
○ 2026-08-09 12:26:46
●A159.203.169.22026-04-05 → 2026-08-09 · 3 obs
● 2026-04-05 23:36:52
● 2026-08-09 12:26:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bigdypper.com | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | 3 records |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bigdypper.com (unsigned zone)
⏱️ Timing
Total: 258ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 159.203.169.2 |
| NS | 3 | ns3.digitalocean.com, ns1.digitalocean.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.digitalocean.com hostmaster.bigdyppe |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com)
Analysis
IP Addresses
bigdypper.com resolves to one IP address: 159.203.169.2.
Name Servers
The authoritative name servers for bigdypper.com are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
bigdypper.com has at least partial name server overlap with other domains, such as biloxiwhitepillars.com, robinschouten.com, finneotech.com and two others.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
bigdypper.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
bigdypper.com has at least partial mail server overlap with other domains such as ns500731.ns500671.ns500754.ns500754.ns500731.ns500688.ns500705.ns500671.ns500704.ns500688.ns500678.ns500666.ns500153.tenderladiesbz.com, ns500742.ns500742.ns500754.ns500754.ns500742.ns500688.ns500671.ns500678.ns500291.ns500671.ns500649.ns500649.ns500666.tenderladiesbz.com, ns500671.ns500731.ns500754.ns500742.ns500671.ns500731.ns500671.ns500671.ns500742.ns500705.ns500291.lustychickser.com and two more.
The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 173.194.45.26 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.