redring.mx - robtex.com
redring.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.summaconsulting.link ⚠️ Not in zone NS records | ||||||
| A | 165.140.69.65🇺🇸 NAMEHERO-KCDC-01165.140.69.0/24 Name Hero, LLC | ||||||
| PTR | vps50704.nodevm.com | ||||||
| NS | ns2.summaconsulting.link ⚠️ Not in zone NS records | ||||||
| A | 165.140.69.65🇺🇸 NAMEHERO-KCDC-01165.140.69.0/24 Name Hero, LLC | ||||||
| PTR | vps50704.nodevm.com | ||||||
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=1785044915 | ||||||
Same first word
redring.com |
redring.mx |
redring.co.at |
redring.at |
redring.net |
redring.co.uk |
redring.sk |
redring.com.mx |
redring.cn |
redring.cz |
Similar names
DNS History
16 records (2 active, 14 former)
○NSns-mx.1and1-dns.biz2015-08-22 → 2017-04-03 · 4 obs
● 2015-08-22 14:42:18
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
○NSns-mx.1and1-dns.com2015-08-22 → 2017-04-03 · 4 obs
● 2015-08-22 14:42:18
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
○NSns-mx.1and1-dns.mx2015-08-22 → 2017-04-03 · 4 obs
● 2015-08-22 14:42:18
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
○NSns-mx.1and1-dns.org2015-08-22 → 2017-04-03 · 4 obs
● 2015-08-22 14:42:18
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
● 2017-04-03 09:59:56
○ 2020-03-20 05:50:04
○ 2026-07-26 05:56:32
●NSns1.summaconsulting.link2026-06-10 → 2026-07-26 · 3 obs
○ 2020-03-20 05:50:04
● 2026-06-10 01:54:14
● 2026-07-26 05:56:32
● 2026-06-10 01:54:14
● 2026-07-26 05:56:32
○NSns1082.ui-dns.biz2020-03-20 → 2020-03-20 · 4 obs
○ 2017-04-03 09:59:56
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○NSns1082.ui-dns.com2020-03-20 → 2020-03-20 · 4 obs
○ 2017-04-03 09:59:56
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○NSns1082.ui-dns.de2020-03-20 → 2020-03-20 · 4 obs
○ 2017-04-03 09:59:56
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○NSns1082.ui-dns.org2020-03-20 → 2020-03-20 · 4 obs
○ 2017-04-03 09:59:56
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
●NSns2.summaconsulting.link2026-06-10 → 2026-07-26 · 3 obs
○ 2020-03-20 05:50:04
● 2026-06-10 01:54:14
● 2026-07-26 05:56:32
● 2026-06-10 01:54:14
● 2026-07-26 05:56:32
○MXmx00.1and1.mx2015-08-22 → 2020-03-20 · 4 obs
● 2015-08-22 14:42:18
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○MXmx01.1and1.mx2015-08-22 → 2020-03-20 · 4 obs
● 2015-08-22 14:42:18
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○A198.71.48.1912015-08-22 → 2016-04-02 · 4 obs
● 2015-08-22 14:42:18
● 2016-04-02 13:30:38
○ 2016-09-08 23:31:32
○ 2026-07-26 05:56:32
● 2016-04-02 13:30:38
○ 2016-09-08 23:31:32
○ 2026-07-26 05:56:32
○A2607:f1c0:1000:618f:7926:cac:2ab9:80022015-08-22 → 2016-04-02 · 4 obs
● 2015-08-22 14:42:18
● 2016-04-02 13:30:38
○ 2016-09-08 23:31:32
○ 2026-07-26 05:56:32
● 2016-04-02 13:30:38
○ 2016-09-08 23:31:32
○ 2026-07-26 05:56:32
○A2607:f1c0:1000:618f:8445:ed88:166f:40212016-09-08 → 2020-03-20 · 5 obs
○ 2016-04-02 13:30:38
● 2016-09-08 23:31:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2016-09-08 23:31:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
○A74.208.215.1072016-09-08 → 2020-03-20 · 5 obs
○ 2016-04-02 13:30:38
● 2016-09-08 23:31:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
● 2016-09-08 23:31:32
● 2020-03-20 05:50:04
○ 2026-06-10 01:54:14
○ 2026-07-26 05:56:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| redring.mx | ns1.summaconsulting.link, ns2.summaconsulting.link | - |
✅ Authoritative Response
Server:165.140.69.65
NS records: ns1.summaconsulting.link, ns2.summaconsulting.link
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for redring.mx (unsigned zone)
⏱️ Timing
Total: 562ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
redring.mx is served by two delegated name servers, ns1.summaconsulting.link and ns2.summaconsulting.link.
Other domains share the same name server configuration as redring.mx, for example motours.com.mx.
ns1.summaconsulting.link and ns2.summaconsulting.link share one IP address between them — 165.140.69.65.
These two host names — ns1.summaconsulting.link and ns2.summaconsulting.link — each point to 165.140.69.65 IP addresses.