theleadsignals.com - robtex.com
theleadsignals.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=1777101131 | ||||||
Same first word
theleadsignals.com |
DNS History
9 records (9 active, 0 former)
●NSns43.domaincontrol.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●NSns44.domaincontrol.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●MXalt1.aspmx.l.google.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●MXalt2.aspmx.l.google.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●MXalt3.aspmx.l.google.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●MXalt4.aspmx.l.google.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●MXaspmx.l.google.com2026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●A15.197.142.1732026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
●A3.33.152.1472026-03-18 → 2026-04-25 · 2 obs
● 2026-04-25 07:18:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net... | - |
| theleadsignals.com | ns43.domaincontrol.com, ns44.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.22
NS records: ns43.domaincontrol.com, ns44.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for theleadsignals.com (unsigned zone)
⏱️ Timing
Total: 182ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.142.173, 3.33.152.147 |
| NS | 2 | ns43.domaincontrol.com, ns44.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=NDsWt3Fv8fRvSyt, v=spf1 include:dc-aa8e722993._spfm.thele |
| SOA | 1 | ns43.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns43.domaincontrol.com, ns43.domaincontrol.com, ns44.domaincontrol.com...)
Analysis
IP Addresses
The entity theleadsignals.com points to two IP numbers: 3.33.152.147 and 15.197.142.173.
For instance, other host names thereip.com, davefulkerson.com, canadait.net, ocius.com and computerclinic.com.au share IP numbers with theleadsignals.com.
Name Servers
theleadsignals.com is delegated to two name servers: ns43.domaincontrol.com and ns44.domaincontrol.com.
theleadsignals.com uses the same name server setup as other domains such as prosperitycdc.org, djaqeel.com, gramata.com, buyhomesinvancouver.com and cenaze-firmasi.info.
theleadsignals.com shares name servers with other domains at least partially, for example primeconnect.co.uk.
Host names with two IP numbers:
ns43.domaincontrol.com points to 2603:5:2152::16 and 97.74.101.22; ns44.domaincontrol.com points to 2603:5:2252::16 and 173.201.69.22.
Mail Servers
Five mail servers handle theleadsignals.com: 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.
theleadsignals.com shares mail servers with other domains at least partially; for instance salehere.co.th, woohoo.mobi, ns500754.ns500671.ns500754.ns500671.ns500742.ns500671.ns500742.ns500705.ns500671.ns500705.ns500705.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500731.ns500754.ns500671.ns500754.ns500742.ns500731.ns500705.ns500671.ns500678.ns500671.ns500671.lusty(0x736c7574)z.com and ns500731.ns500754.ns500731.ns500671.ns500671.ns500705.ns500704.ns500688.ns500688.ns500688.ns500649.ns500671.lusty(0x736c7574)z.com.
these mail servers are commonly used alongside aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4023:c0d::1a and 142.250.101.27
alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.26
alt2.aspmx.l.google.com points to 2a00:1450:400b:c02::1b and 172.253.116.27
alt3.aspmx.l.google.com points to 2607:f8b0:4023:1015::1a and 172.253.135.27
alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.27