dinglabs.com - dns.ninja
dinglabs.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=1784902662 | ||||||
Same first word
dinglabs.com |
Similar names
blingads.com |
landisbg.com |
biglands.co.uk |
signaldb.com |
biglands.com |
biglands.net |
adsbling.com |
biglands.us |
labdsign.com |
adslbing.com |
DNS History
10 records (9 active, 1 former)
●NSns35.domaincontrol.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●NSns36.domaincontrol.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●MXalt1.aspmx.l.google.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●MXalt2.aspmx.l.google.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●MXaspmx.l.google.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●MXaspmx2.googlemail.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●MXaspmx3.googlemail.com2015-06-06 → 2026-07-24 · 2 obs
● 2026-07-24 14:35:22
●A15.197.225.1282026-03-31 → 2026-07-24 · 3 obs
● 2026-03-31 02:36:44
● 2026-07-24 14:35:22
○A184.168.221.72015-06-06 → 2017-04-20 · 4 obs
● 2017-04-20 05:32:42
○ 2026-03-31 02:36:44
○ 2026-07-24 14:35:22
●A3.33.251.1682026-03-31 → 2026-07-24 · 3 obs
● 2026-03-31 02:36:44
● 2026-07-24 14:35:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, l.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net... | - |
| dinglabs.com | ns35.domaincontrol.com, ns36.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.75.18
NS records: ns35.domaincontrol.com, ns36.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dinglabs.com (unsigned zone)
⏱️ Timing
Total: 401ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| TXT | 1 | google-site-verification=yPcgxlRZcX3QiZ9 |
| SOA | 1 | ns35.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)
Analysis
IP Addresses
dinglabs.com has two IP addresses: 3.33.251.168 and 15.197.225.128
Additional host names — humbl.co, charlespenzone.com, mnahub.com and two others — share IP numbers with dinglabs.com.
Name Servers
dinglabs.com uses two name servers for its delegation: ns35.domaincontrol.com and ns36.domaincontrol.com.
dinglabs.com shares its name server setup with other domains, including mayl.co.uk, labgenomic.com, crf-inc.com and two others.
At least some of dinglabs.com's name servers are also used by other domains, among them stlzoo.net.
The two host names ns35.domaincontrol.com and ns36.domaincontrol.com each have a pair of IP addresses: ns35.domaincontrol.com has 97.74.107.18 and 2603:5:21b1::12, and ns36.domaincontrol.com has 173.201.75.18 and 2603:5:22b1::12.
Mail Servers
Five mail servers handle dinglabs.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
dinglabs.com shares mail servers — at least in part — with other domains, including tresareas.com, unicask.com, ns500671.ns500742.ns500742.ns500731.ns500754.ns500731.ns500731.ns500731.ns500742.ns500704.ns500671.ns500678.ns500671.ns500291.ns500291.ns500131.lustychickser.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.16.27 and 2607:f8b0:4004:c07::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.