lambda.mu - robtex.com
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=1788551381 | ||||||
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 20:41:32
●NSns2.digitalocean.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●NSns3.digitalocean.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●MXalt1.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●MXalt2.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●MXalt3.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●MXalt4.aspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●MXaspmx.l.google.com2026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
●A204.48.29.02026-09-02 → 2026-09-04 · 2 obs
● 2026-09-04 20:41:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mu | v0n3.tld.mu, v2n0.tld.mu, v0n0.tld.mu, v0n2.tld.mu... | 12 records |
| lambda.mu | ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns3.digitalocean.com, ns2.digitalocean.com, ns1.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lambda.mu (unsigned zone)
⏱️ Timing
Total: 580ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 204.48.29.0 |
| NS | 3 | ns1.digitalocean.com, ns3.digitalocean.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.digitalocean.com hostmaster.lambda.m |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n1.tld.mu, v2n0.tld.mu, v0n3.tld.mu...)
Analysis
IP Addresses
lambda.mu resolves to just one IP address, 204.48.29.0.
Name Servers
lambda.mu is delegated to three name servers: 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 each resolve to two IP addresses: ns1.digitalocean.com resolves to 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com resolves to 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com resolves 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.
There is at least a partial MX overlap between lambda.mu and other domains, including thelearnerscircle.com, landsberg.co.za, miko-robot.in and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com points to 142.251.16.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com points to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com points to 172.253.157.27 and 2a00:1450:400c:c23::1a.