leadcrowd.com - robtex.com
leadcrowd.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=1771291435 | ||||||
Same first word
leadcrowd.com |
Similar names
DNS History
21 records (12 active, 9 former)
●NSns-1158.awsdns-16.org2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●NSns-1578.awsdns-05.co.uk2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●NSns-297.awsdns-37.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●NSns-678.awsdns-20.net2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
○NSns1.uniregistrymarket.link2017-02-20 → 2020-02-13 · 4 obs
● 2020-02-13 18:35:20
○ 2026-02-16 23:57:50
○ 2026-02-24 16:30:02
○NSns2.uniregistrymarket.link2017-02-20 → 2020-02-13 · 4 obs
● 2020-02-13 18:35:20
○ 2026-02-16 23:57:50
○ 2026-02-24 16:30:02
●MXalt1.aspmx.l.google.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●MXalt2.aspmx.l.google.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●MXalt3.aspmx.l.google.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●MXalt4.aspmx.l.google.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
●MXaspmx.l.google.com2026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
○MXmx247.in-mx.com2020-02-13 → 2020-02-13 · 3 obs
○ 2026-02-16 23:57:50
○ 2026-02-24 16:30:02
○MXmx247.in-mx.net2020-02-13 → 2020-02-13 · 3 obs
○ 2026-02-16 23:57:50
○ 2026-02-24 16:30:02
○A18.132.185.1272026-02-16 → 2026-02-24 · 2 obs
○ 2026-02-24 16:30:02
○A18.133.0.362026-02-16 → 2026-02-16 · 4 obs
● 2026-02-16 23:57:50
○ 2026-02-19 19:53:16
○ 2026-02-24 16:30:02
○A18.133.213.922026-02-16 → 2026-02-24 · 2 obs
○ 2026-02-24 16:30:02
●A18.135.140.1072026-02-19 → 2026-02-24 · 3 obs
● 2026-02-19 19:53:16
● 2026-02-24 16:30:02
●A18.170.135.712026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
○A3.9.45.442026-02-16 → 2026-02-24 · 2 obs
○ 2026-02-24 16:30:02
●A35.177.0.242026-02-16 → 2026-02-24 · 3 obs
● 2026-02-16 23:57:50
● 2026-02-24 16:30:02
○A69.172.201.1532017-02-20 → 2020-02-13 · 4 obs
● 2020-02-13 18:35:20
○ 2026-02-16 23:57:50
○ 2026-02-24 16:30:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| leadcrowd.com | ns-678.awsdns-20.net, ns-297.awsdns-37.com, ns-1578.awsdns-05.co.uk, ns-1158.awsdns-16.org | 1 record |
✅ Authoritative Response
Server: 205.251.194.166
NS records: ns-678.awsdns-20.net, ns-297.awsdns-37.com, ns-1578.awsdns-05.co.uk, ns-1158.awsdns-16.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadcrowd.com (unsigned zone)
⏱️ Timing
Total: 583ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 18.170.135.71, 18.135.140.107... |
| NS | 4 | ns-1158.awsdns-16.org, ns-1578.awsdns-05.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 5 | brevo-code:f09cc0e4e9a3d4120f5eafade9b1b, google-site-verification=95SQlpPmbcjr0vr... |
| SOA | 1 | ns-1578.awsdns-05.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 1
Out-of-bailiwick: 1 (ns-297.awsdns-37.com)
AI analysis
leadcrowd.com resolves to three IP numbers: 18.135.140.107, 18.170.135.71 and 35.177.0.24.
Other host names, for instance mortgage-rates.uk, ec2-18-135-140-107.eu-west-2.compute.amazonaws.com, pension-deals.com, remortgage-rates.co.uk and teito.co.uk share IP numbers with leadcrowd.com.
leadcrowd.com is delegated to four name servers: ns-297.awsdns-37.com, ns-678.awsdns-20.net, ns-1158.awsdns-16.org and ns-1578.awsdns-05.co.uk.
leadcrowd.com shares some name servers with other domains, for example dwascreenings.com, zkai.co.jp, paulabascal.com, screenwritingdirectory.com and trinnvis.io.
These name servers are often used together with ns-507.awsdns-63.com, ns-1390.awsdns-45.org and ns-2022.awsdns-60.co.uk.
Host names with two IP numbers
Two IPs per host:
ns-297.awsdns-37.com points to 2600:9000:5301:2900::1 and 205.251.193.41
ns-678.awsdns-20.net points to 2600:9000:5302:a600::1 and 205.251.194.166
ns-1158.awsdns-16.org points to 2600:9000:5304:8600::1 and 205.251.196.134
ns-1578.awsdns-05.co.uk points to 2600:9000:5306:2a00::1 and 205.251.198.42
leadcrowd.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
leadcrowd.com shares some mail servers with other domains, at least partially; for instance socialhealthexperts.com, cheatdaydesign.com, ns500742.ns500731.ns500671.ns500671.ns500671.ns500742.ns500742.ns500678.ns500705.ns500291.ns500291.ns500649.ns500142.lusty(0x736c7574)z.com, ns500768.ns500698.ns500698.ns500698.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500708.ns500686.ns500619.ns500619.ns500576.trackreceptor.com and flattopbob.com.
these mail servers are often used together with the mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IPs:
Host aspmx.l.google.com has IPs 2607:f8b0:4004:c19::1b and 172.253.62.27.
Host alt1.aspmx.l.google.com has IPs 2607:f8b0:4003:c30::1b and 74.125.27.26.
Host alt2.aspmx.l.google.com has IPs 2607:f8b0:4001:c70::1a and 192.178.209.26.
Host alt3.aspmx.l.google.com has IPs 2607:f8b0:4024:c0d::1b and 192.178.152.26.
Host alt4.aspmx.l.google.com has IPs 2607:f8b0:4023:403::1a and 142.250.96.27.