renaultkwid.mx - dns.ninja
renaultkwid.mx
mx
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | m.mx-ns.mx ⭐ | ||||||
| NS | c.mx-ns.mx | ||||||
| NS | e.mx-ns.mx | ||||||
| NS | i.mx-ns.mx | ||||||
| NS | o.mx-ns.mx | ||||||
| NS | x.mx-ns.mx | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1786035096 | ||||||
Same first word
renaultkwid.fr |
renaultkwid.com.br |
renaultkwid.com |
renaultkwid.mx |
renaultkwid.co.in |
renaultkwid.in |
renaultkwid.it |
renaultkwid.ec |
renaultkwid.net |
DNS History
9 records (9 active, 0 former)
●NSindom10.indomco.com2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●NSindom130.indomco.org2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●NSindom20.indomco.net2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●NSindom30.indomco.fr2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●NSindom80.indomco.hk2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●MXrelay1.netnames.net2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●MXrelay2.netnames.net2026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●A165.160.13.202026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
●A165.160.15.202026-06-09 → 2026-08-06 · 2 obs
● 2026-08-06 17:08:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| renaultkwid.mx | indom10.indomco.com, indom20.indomco.net, indom30.indomco.fr, indom80.indomco.hk... | - |
✅ Authoritative Response
Server:156.154.131.100
NS records: indom10.indomco.com, indom20.indomco.net, indom30.indomco.fr, indom80.indomco.hk, indom130.indomco.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for renaultkwid.mx (unsigned zone)
⏱️ Timing
Total: 1266ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.13.20, 165.160.15.20 |
| NS | 5 | indom10.indomco.com, indom20.indomco.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 10) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | indom10.indomco.com hostmaster.cscdns.ne |
Analysis
IP Addresses
renaultkwid.mx directs to two IP numbers, 165.160.13.20 and 165.160.15.20
Two other host names, along with o800flowers.com, atkinsglobal.com.au and horseandco.net, also share IP numbers with renaultkwid.mx.
Name Servers
renaultkwid.mx delegates to five name servers: indom10.indomco.com, indom30.indomco.fr, indom80.indomco.hk and two others.
renaultkwid.mx partially shares its NS delegation with several other domains, including rci-bank.fr, saatchi-health.fr, fr2-preprod.fr and two others.
The name servers indom20.indomco.net, indom130.indomco.org, dns1.cscdns.net and dns2.cscdns.net are often found in use alongside these name servers.
Host names that have two IP addresses:
indom10.indomco.com resolves to two addresses: 156.154.130.100 and 2610:a1:1022::100.
indom30.indomco.fr resolves to two addresses: 156.154.130.100 and 2610:a1:1022::100.
indom80.indomco.hk resolves to two addresses: 156.154.131.100 and 2610:a1:1023::100.
indom20.indomco.net resolves to two addresses: 156.154.131.100 and 2610:a1:1023::100.
indom130.indomco.org resolves to two addresses: 156.154.130.100 and 2610:a1:1022::100.
Each of indom10.indomco.com, indom30.indomco.fr and indom130.indomco.org resolves to 2610:a1:1022::100.
Each of indom10.indomco.com, indom30.indomco.fr and indom130.indomco.org resolves to 156.154.130.100.
indom80.indomco.hk along with indom20.indomco.net each resolve to 2610:a1:1023::100 IP addresses.
indom80.indomco.hk along with indom20.indomco.net each resolve to 156.154.131.100 IP addresses.
Mail Servers
renaultkwid.mx is served by two mail servers, relay1.netnames.net and relay2.netnames.net.
Among the domains sharing a mail server setup with renaultkwid.mx are paybybankapp.com, apostenadiversao.com.br, biomettechnology.com and two others.
renaultkwid.mx partially shares its mail servers with other domains, exotix.org and cargopartner.in being examples.
relay1.netnames.net resolves to 185.26.230.83. relay2.netnames.net resolves to 185.26.230.89. Both host names point to a single IP number.