spooley.com - robtex.com
spooley.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=1786589334 | ||||||
Same first word
Similar names
DNS History
10 records (9 active, 1 former)
●NSns0.lcn.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●NSns1.lcn.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●NSns2.lcn.com2020-02-09 → 2026-08-13 · 3 obs
● 2020-02-09 01:05:48
● 2026-08-13 03:20:08
●MXalt1.aspmx.l.google.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●MXalt2.aspmx.l.google.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●MXaspmx.l.google.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●MXaspmx2.googlemail.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
●MXaspmx3.googlemail.com2015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
○MXmailforward.lcn.com2015-07-05 → 2020-02-09 · 5 obs
● 2015-07-05 03:28:12
● 2020-02-09 01:05:48
○ 2026-06-29 20:24:30
○ 2026-08-13 03:20:08
●A81.2.80.2172015-07-05 → 2026-08-13 · 3 obs
● 2015-07-05 03:28:12
● 2026-08-13 03:20:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net, d.gtld-servers.net... | - |
| spooley.com | ns0.lcn.com, ns1.lcn.com, ns2.lcn.com | 3 records |
✅ Authoritative Response
Server:85.233.160.69
NS records: ns0.lcn.com, ns1.lcn.com, ns2.lcn.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for spooley.com (unsigned zone)
⏱️ Timing
Total: 368ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 81.2.80.217 |
| NS | 3 | ns2.lcn.com, ns1.lcn.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), aspmx2.googlemail.com (pri: 10)... |
| TXT | 2 | google-site-verification=CWPRre6QddlLdzV, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns0.lcn.com support.lcn.com |
📌 Glue Records Collected
Total: 3
Out-of-bailiwick: 3 (ns0.lcn.com, ns1.lcn.com, ns2.lcn.com)
Analysis
IP Addresses
spooley.com resolves to one IP address: 81.2.80.217.
Name Servers
The authoritative name servers for spooley.com are ns0.lcn.com, ns1.lcn.com and ns2.lcn.com — three in total.
spooley.com shares at least some of its name servers with other domains, including blackmagick.co.uk, 48wimpole.co.uk, coyoti.com and two others.
These name servers are frequently seen alongside the name servers ns0.telivo.com, ns1.telivo.com, ns0.lcn.biz and ns1.lcn.biz.
The hostnames ns0.lcn.com, ns1.lcn.com and ns2.lcn.com each resolve to a single IP: ns0.lcn.com → 195.110.124.234, ns1.lcn.com → 85.233.160.69, ns2.lcn.com → 91.186.2.8.
Mail Servers
spooley.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
spooley.com has at least partial mail server overlap with other domains such as ns500758.ns500758.ns500758.ns500698.ns500759.ns500736.ns500698.ns500735.ns500576.ns500576.ns500708.ns500698.ns500619.ns500576.trackreceptor.com, ns500759.ns500758.ns500698.ns500759.ns500736.ns500698.ns500698.ns500698.ns500708.ns500708.ns500698.ns500686.ns500619.ns500619.trackreceptor.com, ns500759.ns500759.ns500758.ns500758.ns500759.ns500698.ns500698.ns500708.ns500708.ns500576.ns500698.ns500686.ns500576.ns500619.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c29::1a.
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.27 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c14::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.