leadloop.co - dns.ninja
leadloop.co
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759775355 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
10 records (10 active, 0 former)
●NSns-cloud-e1.googledomains.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●NSns-cloud-e2.googledomains.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●NSns-cloud-e3.googledomains.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●NSns-cloud-e4.googledomains.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●MXalt1.aspmx.l.google.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●MXalt2.aspmx.l.google.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●MXalt3.aspmx.l.google.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●MXalt4.aspmx.l.google.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●MXaspmx.l.google.com2026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
●A216.198.79.12026-09-25 → 2026-10-07 · 2 obs
● 2026-10-07 08:58:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co | 8 records |
| leadloop.co | ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com | - |
✅ Authoritative Response
Server:216.239.38.110
NS records: ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e1.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 820ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.198.79.1 |
| NS | 4 | ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a.registrydns.co, a.registrydns.co, b.registrydns.co...)
Analysis
IP Addresses
leadloop.co resolves to one IP address: 216.198.79.1.
aiconsultinggroups.com, alloia.app, urbangriddevelopers.com and two other host names share IP numbers with leadloop.co.
Name Servers
The authoritative name servers for leadloop.co are ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
leadloop.co has at least partial name server overlap with other domains, such as antidietnutrition.com, fortiergermane.com, stoicallybuilt.com and two others.
It is common to see these name servers used together with name servers ns1.mirusresearch.com and ns2.mir.us.
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 leadloop.co is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
leadloop.co has at least partial mail server overlap with other domains such as nikotrans.se, rootalot.com, novax.com.br and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 142.251.111.27 and 2607:f8b0:4004:c29::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 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.