letsnode.io - robtex.com
letsnode.io
io
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a0.nic.io β | ||||||
| NS | a2.nic.io | ||||||
| NS | b0.nic.io | ||||||
| NS | c0.nic.io | ||||||
| SOA | a0.nic.iohostmaster@donuts.email serial=1794128659 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
7 records (7 active, 0 former)
βNSns1cwy.name.com2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
βNSns2clp.name.com2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
βNSns3gxy.name.com2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
βNSns4htz.name.com2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
βMXmx1.titan.email2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
βMXmx2.titan.email2026-08-31 β 2026-11-08 Β· 2 obs
β 2026-11-08 09:27:32
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | c0.nic.io, a2.nic.io, a0.nic.io, b0.nic.io | - |
| letsnode.io | ns1cwy.name.com, ns2clp.name.com, ns3gxy.name.com, ns4htz.name.com | - |
β Authoritative Response
Server:163.114.217.49
NS records: ns1cwy.name.com, ns2clp.name.com, ns3gxy.name.com, ns4htz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for letsnode.io (unsigned zone)
β±οΈ Timing
Total: 701ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1cwy.name.com, ns2clp.name.com... |
| MX | 2 | mx1.titan.email (pri: 10), mx2.titan.email (pri: 20) |
| TXT | 1 | v=spf1 include:spf.titan.email ~all |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Name Servers
Five name servers handle delegation for letsnode.io: ns1.name.com, ns1cwy.name.com, ns2clp.name.com and two others.
The name servers of letsnode.io overlap at least partially with those of other domains β among them tytusfieldtech.com, vermontismoldy.com, healthrix.net and two more.
These name servers commonly appear in delegations together with ns3gxy.name.com, ns4htz.name.com, ns1hwy.name.com and 7 other.
Host names pointing to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1cwy.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2clp.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3gxy.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4htz.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1cwy.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1cwy.name.com each resolve to 163.114.216.17 IP addresses.
Mail Servers
letsnode.io uses two mail servers, mx1.titan.email and mx2.titan.email.
The mail server setup of letsnode.io matches that of other domains such as 101perfume.com, fundacionmiradentro.org, akulasports.com.br and two others.
letsnode.io has mail servers in common with other domains β claryti.co being one example.
mx1.titan.email and mx2.titan.email both direct to 32.198.149.193, 98.95.157.19 and 184.196.249.169, all three IP addresses being shared between the two hosts.
mx1.titan.email along with mx2.titan.email each resolve to 32.198.149.193 IP addresses.
mx1.titan.email along with mx2.titan.email each resolve to 98.95.157.19 IP addresses.
mx1.titan.email along with mx2.titan.email each resolve to 184.196.249.169 IP addresses.