lem.dev - robtex.com
lem.dev
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
leivers.dev |
leji.dev |
lejtzen.dev |
lekan.dev |
lekepay.dev |
lekker.dev |
lekkerai.dev |
leko.dev |
lekro.dev |
lekta.dev |
lektra.dev |
lel190.dev |
lele.dev |
lelecode.dev |
lelekdev.dev |
lelered.dev |
lellol.dev |
leloy.dev |
leluli.dev |
Next names
DNS History
10 records (10 active, 0 former)
●NSns-cloud-e1.googledomains.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●NSns-cloud-e2.googledomains.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●NSns-cloud-e3.googledomains.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●NSns-cloud-e4.googledomains.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●MXalt1.aspmx.l.google.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●MXalt2.aspmx.l.google.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●MXalt3.aspmx.l.google.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●MXalt4.aspmx.l.google.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●MXaspmx.l.google.com2026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
●A160.16.132.2172026-08-19 → 2026-08-24 · 2 obs
● 2026-08-24 11:10:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| lem.dev | ns-cloud-e3.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com | - |
✅ Authoritative Response
Server:216.239.34.110
NS records: ns-cloud-e3.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1288ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.16.132.217 |
| NS | 4 | ns-cloud-e1.googledomains.com, ns-cloud-e3.googledomains.com... |
| MX | 5 | alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
lem.dev directs to one IP number, which is 160.16.132.217.
Name Servers
The domain lem.dev is delegated to these four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
lem.dev has at least partial name server overlap with other domains, such as theartillerymeet.com, rebelvis.com, bjsbrothersmx.com and two others.
ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com all point to exactly two IP numbers each: ns-cloud-e1.googledomains.com → 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com → 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com → 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com → 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
Mail for lem.dev is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
lem.dev shares at least some of its mail servers with other domains — for example oaecheer.com, epo.com.az, legacyhomeservicessocal.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
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::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.