leadbatchteam.com - dns.ninja
leadbatchteam.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=1790187569 | ||||||
Same first word
leadbatchteam.com |
Similar names
Previous names
Next names
DNS History
5 records (5 active, 0 former)
●NSns-cloud-b1.googledomains.com2026-08-31 → 2026-09-23 · 2 obs
● 2026-09-23 18:41:02
●NSns-cloud-b2.googledomains.com2026-08-31 → 2026-09-23 · 2 obs
● 2026-09-23 18:41:02
●NSns-cloud-b3.googledomains.com2026-08-31 → 2026-09-23 · 2 obs
● 2026-09-23 18:41:02
●NSns-cloud-b4.googledomains.com2026-08-31 → 2026-09-23 · 2 obs
● 2026-09-23 18:41:02
●MXmailserver.purelymail.com2026-08-31 → 2026-09-23 · 2 obs
● 2026-09-23 18:41:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net... | - |
| leadbatchteam.com | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.107
NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadbatchteam.com (unsigned zone)
⏱️ Timing
Total: 366ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com... |
| MX | 1 | mailserver.purelymail.com (pri: 50) |
| TXT | 2 | purelymail_ownership_proof=333e720b77348, v=spf1 include:_spf.purelymail.com ~all |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)
Analysis
Name Servers
Four name servers handle the delegation for leadbatchteam.com: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
leadbatchteam.com partially shares its NS delegation with several other domains, including rendslargent.eu, noctuarycurio.com, elsaroberts.com and two others.
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com each carry two IP addresses. ns-cloud-b1.googledomains.com has 216.239.32.107 and 2001:4860:4802:32::6b; ns-cloud-b2.googledomains.com has 216.239.34.107 and 2001:4860:4802:34::6b; ns-cloud-b3.googledomains.com has 216.239.36.107 and 2001:4860:4802:36::6b; ns-cloud-b4.googledomains.com has 216.239.38.107 and 2001:4860:4802:38::6b.
Mail Servers
leadbatchteam.com uses one mail server — mailserver.purelymail.com.
The mail server setup of leadbatchteam.com matches that of other domains such as baroneholding.com, usereeva.com, bewerbertag-landkreis.com and two others.
The MX records for leadbatchteam.com are at least partially shared with other domains, such as ludeia.com, callitweb.com, rooferstoronto.ca and laudeus.ca.
There is one IP number for mailserver.purelymail.com: 18.204.123.63.