littymail.com - dns.ninja
littymail.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=1783764447 | ||||||
Same first word
littymail.com |
DNS History
11 records (6 active, 5 former)
●NSns-cloud-e1.googledomains.com2018-05-13 → 2026-07-11 · 2 obs
● 2026-07-11 10:26:46
●NSns-cloud-e2.googledomains.com2018-05-13 → 2026-07-11 · 2 obs
● 2026-07-11 10:26:46
●NSns-cloud-e3.googledomains.com2018-05-13 → 2026-07-11 · 2 obs
● 2026-07-11 10:26:46
●NSns-cloud-e4.googledomains.com2018-05-13 → 2026-07-11 · 2 obs
● 2026-07-11 10:26:46
○MXalt1.gmr-smtp-in.l.google.com2018-05-13 → 2018-05-13 · 2 obs
○ 2026-07-11 10:26:46
○MXalt2.gmr-smtp-in.l.google.com2018-05-13 → 2018-05-13 · 2 obs
○ 2026-07-11 10:26:46
○MXalt3.gmr-smtp-in.l.google.com2018-05-13 → 2018-05-13 · 2 obs
○ 2026-07-11 10:26:46
○MXalt4.gmr-smtp-in.l.google.com2018-05-13 → 2018-05-13 · 2 obs
○ 2026-07-11 10:26:46
○MXgmr-smtp-in.l.google.com2018-05-13 → 2018-05-13 · 2 obs
○ 2026-07-11 10:26:46
●MXmxa.mailgun.org2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 10:26:46
●MXmxb.mailgun.org2026-07-11 → 2026-07-11 · 2 obs
● 2026-07-11 10: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... | - |
| littymail.com | ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.38.110
NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for littymail.com (unsigned zone)
⏱️ Timing
Total: 228ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com... |
| MX | 2 | mxa.mailgun.org (pri: 10), mxb.mailgun.org (pri: 10) |
| TXT | 1 | v=spf1 include:mailgun.org ~all |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)
Analysis
Name Servers
The NS records for littymail.com point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
littymail.com has at least partial name server overlap with other domains, such as meloon.net, mirakaplan.com, artieandsons.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
littymail.com is served by two mail servers, mxa.mailgun.org and mxb.mailgun.org.
Among the domains sharing a mail server setup with littymail.com are oktie.com, crab-battle.com, mail.bitforged.net and two others.
There is at least a partial MX overlap between littymail.com and other domains, including jarhq.com, johnsonandtowers.com, rosyama.ru and two others.
These mail servers tend to be used in combination with the mail servers aspmx.l.google.com and alt1.aspmx.l.google.com.
mxa.mailgun.org directs to 34.36.182.139 and mxb.mailgun.org directs to 34.149.254.5; each host name points to exactly one IP number.