leadbatchmail.com - dns.ninja
leadbatchmail.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=1788782703 | ||||||
Same first word
leadbatchmail.com |
Previous names
Next names
DNS History
5 records (5 active, 0 former)
●NSns-cloud-e1.googledomains.com2026-09-05 → 2026-09-07 · 2 obs
● 2026-09-07 12:17:32
●NSns-cloud-e2.googledomains.com2026-09-05 → 2026-09-07 · 2 obs
● 2026-09-07 12:17:32
●NSns-cloud-e3.googledomains.com2026-09-05 → 2026-09-07 · 2 obs
● 2026-09-07 12:17:32
●NSns-cloud-e4.googledomains.com2026-09-05 → 2026-09-07 · 2 obs
● 2026-09-07 12:17:32
●MXmailserver.purelymail.com2026-09-05 → 2026-09-07 · 2 obs
● 2026-09-07 12:17:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net... | - |
| leadbatchmail.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.36.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 leadbatchmail.com (unsigned zone)
⏱️ Timing
Total: 268ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com... |
| MX | 1 | mailserver.purelymail.com (pri: 50) |
| TXT | 2 | v=spf1 include:_spf.purelymail.com ~all, purelymail_ownership_proof=333e720b77348 |
| 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
Four name servers handle the delegation for leadbatchmail.com: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
The name servers of leadbatchmail.com overlap at least partially with those of other domains — among them masculinity3.com, takeuchi-shika.net, steadyhandsva.info and two more.
Each of the four hosts ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com has two IP addresses. ns-cloud-e1.googledomains.com points to 216.239.32.110 and 2001:4860:4802:32::6e. ns-cloud-e2.googledomains.com points to 216.239.34.110 and 2001:4860:4802:34::6e. ns-cloud-e3.googledomains.com points to 216.239.36.110 and 2001:4860:4802:36::6e. ns-cloud-e4.googledomains.com points to 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
leadbatchmail.com uses one mail server — mailserver.purelymail.com.
The mail server setup of leadbatchmail.com matches that of other domains such as myclosingmasters.com, sony-nucleus.com, kycpanama.com and two others.
leadbatchmail.com has mail servers in common with other domains — thedailytakeinc.com being one example.
mailserver.purelymail.com carries a single IP number, which is 18.204.123.63.