lambda.mu - dns.ninja
lambda.mu
mu
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.tld.mu ⭐ | ||||||
| NS | v0n1.tld.mu | ||||||
| NS | v0n2.tld.mu | ||||||
| NS | v0n3.tld.mu | ||||||
| NS | v2n0.tld.mu | ||||||
| NS | v2n1.tld.mu | ||||||
| SOA | v0n0.tld.muhostmaster@donuts.email serial=1788494876 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
9 records (9 active, 0 former)
●NSns1.digitalocean.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●NSns2.digitalocean.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●NSns3.digitalocean.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●MXalt1.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●MXalt2.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●MXalt3.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●MXalt4.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●MXaspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
●A204.48.29.02026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 04:34:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mu | v0n0.tld.mu, v0n1.tld.mu, v0n2.tld.mu, v0n3.tld.mu... | 12 records |
| lambda.mu | ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com | - |
✅ 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 lambda.mu (unsigned zone)
⏱️ Timing
Total: 333ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 204.48.29.0 |
| NS | 3 | ns3.digitalocean.com, ns2.digitalocean.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.digitalocean.com hostmaster.lambda.m |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v0n0.tld.mu, v0n0.tld.mu, v0n1.tld.mu...)
Analysis
IP Addresses
lambda.mu points to a single IP number: 204.48.29.0.
Name Servers
lambda.mu carries NS records delegating to ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.
At least some of lambda.mu's name servers are shared with other domains, for example oscarfridman.com, onetick.co.kr, spendtogether.app and two more.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com are three hostnames that each resolve to a pair of IP addresses: ns1.digitalocean.com to 172.64.52.210 and 2606:4700:52::ac40:34d2, ns2.digitalocean.com to 172.64.53.21 and 2606:4700:5a::ac40:3515, and ns3.digitalocean.com to 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
lambda.mu has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
lambda.mu shares mail servers — at least in part — with other domains, including thelearnerscircle.com, landsberg.co.za, miko-robot.in and two others.
These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com resolves to two addresses: 142.251.163.27 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.