ringlock.com.mx - dns.ninja
ringlock.com.mx
com.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | m.mx-ns.mx ⭐ ⚠️ Not in parent delegation | ||||||
| NS | c.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | e.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | i.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | o.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| NS | x.mx-ns.mx ⚠️ Not in parent delegation | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | m.mx-ns.mxhostmaster@nic.mx serial=1785474148 | ||||||
Same first word
ringlock.vn |
ringlock.jp |
ringlock.com.mx |
ringlock.ch |
ringlock.com |
ringlock.swiss |
ringlock.mx |
ringlock.com.au |
ringlock.co.nz |
Similar names
DNS History
10 records (8 active, 2 former)
●NSns1.jetthost.net2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●NSns2.jetthost.net2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●MXalt1.aspmx.l.google.com2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●MXalt2.aspmx.l.google.com2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●MXaspmx.l.google.com2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●MXaspmx2.googlemail.com2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
●MXaspmx3.googlemail.com2015-09-01 → 2026-07-31 · 2 obs
● 2026-07-31 05:33:18
○A209.236.113.462015-09-01 → 2015-09-26 · 4 obs
● 2015-09-26 22:39:56
○ 2015-12-08 18:43:18
○ 2026-07-31 05:33:18
●A216.158.66.2502026-02-17 → 2026-07-31 · 3 obs
● 2026-02-17 23:16:48
● 2026-07-31 05:33:18
○A67.222.158.1222015-12-08 → 2017-04-18 · 5 obs
● 2015-12-08 18:43:18
● 2017-04-18 22:19:04
○ 2026-02-17 23:16:48
○ 2026-07-31 05:33:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| ringlock.com.mx | ns1.jetthost.net, ns2.jetthost.net | - |
✅ Authoritative Response
Server:172.245.226.125
NS records: ns1.jetthost.net, ns2.jetthost.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ringlock.com.mx (unsigned zone)
⏱️ Timing
Total: 686ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.158.66.250 |
| NS | 2 | ns1.jetthost.net, ns2.jetthost.net |
| MX | 5 | aspmx3.googlemail.com (pri: 30), aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.jetthost.net hostmaster.jetthost.net |
Analysis
IP Addresses
ringlock.com.mx resolves to just one IP address, 216.158.66.250.
Two other host names, along with did.com.mx, godsi.com.mx and dec.olinia.com.mx, also share IP numbers with ringlock.com.mx.
Name Servers
ringlock.com.mx is delegated to two name servers: ns1.jetthost.net and ns2.jetthost.net.
ringlock.com.mx shares its NS records with other domains, for example lyo.com.mx, geseguridad.com, xaid.com.mx and two others.
ns1.jetthost.net directs to 167.88.116.143 and ns2.jetthost.net directs to 172.245.226.125; each host name points to exactly one IP number.
Mail Servers
ringlock.com.mx is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between ringlock.com.mx and other domains, including noblefive.com, skaven.cz, ns500734.ns500693.ns500699.ns500693.ns500734.ns500693.ns500699.ns500728.ns500699.ns500588.ns500699.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com points to 74.125.193.26 and 2a00:1450:400b:c01::1a.
aspmx.l.google.com points to 172.253.62.26 and 2607:f8b0:4004:c21::1b.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 74.125.193.27 and 2a00:1450:400b:c01::1a.
aspmx3.googlemail.com and alt2.aspmx.l.google.com are host names that each point to 2a00:1450:400b:c01::1a IP addresses.