letango.com - dns.ninja
letango.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=1783214366 | ||||||
Same first word
letango.com |
Similar names
DNS History
13 records (8 active, 5 former)
○NS5.56.63.7.dnsgigas.es2016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 11:28:06
○ 2017-10-01 10:21:18
○ 2026-07-05 01:34:14
○NS5.56.63.7.ns2.dnsgigas.es2016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 11:28:06
○ 2017-10-01 10:21:18
○ 2026-07-05 01:34:14
○NSns.letango.com2015-06-07 → 2016-04-18 · 4 obs
● 2016-04-18 22:10:20
○ 2016-12-06 11:28:06
○ 2026-07-05 01:34:14
●NSns1.hostmonster.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●NSns2.hostmonster.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●MXalt1.aspmx.l.google.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●MXalt2.aspmx.l.google.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●MXalt3.aspmx.l.google.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●MXalt4.aspmx.l.google.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
●MXaspmx.l.google.com2017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
○MXmail.letango.com2015-06-07 → 2016-12-06 · 4 obs
● 2016-12-06 11:28:06
○ 2017-10-01 10:21:18
○ 2026-07-05 01:34:14
●A23.227.38.322017-10-01 → 2026-07-05 · 3 obs
● 2017-10-01 10:21:18
● 2026-07-05 01:34:14
○A5.56.63.72015-06-07 → 2016-12-06 · 4 obs
● 2016-12-06 11:28:06
○ 2017-10-01 10:21:18
○ 2026-07-05 01:34:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net... | - |
| letango.com | ns2.hostmonster.com, ns1.hostmonster.com | 2 records |
✅ Authoritative Response
Server:162.159.24.157
NS records: ns2.hostmonster.com, ns1.hostmonster.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for letango.com (unsigned zone)
⏱️ Timing
Total: 553ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.32 |
| NS | 2 | ns1.hostmonster.com, ns2.hostmonster.com |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.hostmonster.com dnsadmin.hostmonster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.hostmonster.com, ns1.hostmonster.com)
Analysis
IP Addresses
letango.com directs to one IP number, which is 23.227.38.32.
Among the host names that share IP numbers with letango.com are theantik.com, suatmm.com, vintagefloralimports.com and two others.
Name Servers
letango.com uses two name servers for its delegation: ns1.hostmonster.com and ns2.hostmonster.com.
letango.com has the same name server delegation as a number of other domains, such as kardoshprojects.com, sanantonioclinic.com, cfmjet.com and two more.
There is an overlap in name servers between letango.com and other domains, for example tecnovap.co, tilivia.com and onglyzaheartattack.net
These name servers commonly appear alongside the name servers ns1.bluehost.com and ns2.bluehost.com.
Both ns1.hostmonster.com and ns2.hostmonster.com have a single IP address each — ns1.hostmonster.com resolves to 162.159.24.157 while ns2.hostmonster.com resolves to 162.159.25.186.
Mail Servers
letango.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
letango.com shares at least some of its mail servers with other domains — for example nayanov.com, thekeithbritt.com, johnacaruso.com and two more.
These mail servers tend to be used in conjunction with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and two additional mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com directs traffic to 172.253.62.26 and 2607:f8b0:4004:c1d::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::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::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.