mx.pe - dns.ninja

mx.pe

DNSSEC⚠️ Not signed
NSns2.rcp.net.pe
A209.45.127.3🇵🇪 AS3132209.45.127.0/24 SP-RCP
PTRichu.rcp.net.pe
NSns.rcp.net.pe
A161.132.17.10🇵🇪 AS3132161.132.17.0/24 PNAP-SEF wowtech-1
PTRns.rcp.net.pe
SOANS.RCP.NET.peOPERADOR@RCP.pe 2024-06-26 #0

pe

DNSSEC🔒 Signed (DS record present)
NSquipu.rcp.net.pe
NSa.lactld.org
NSpch.rcp.pe
NSpe1.dnsnode.net
SOAquipu.rcp.net.peoperador@rcp.pe 2026-07-31 #0

Same first word

Similar names

DNS History

28 records (2 active, 26 former)

20162017201820192020202120222023202420252026NSns.rcp.net.pens2.rcp.net.penadia.ns.cloudflare.comns1.bodis.comns1.routing.netns1.stackdns.comns2.bodis.comns2.routing.netns2.stackdns.comns3.routing.netns3.stackdns.comns4.stackdns.comtheo.ns.cloudflare.comMXmx.stackmail.commx01.routing.netmx02.routing.netmx03.routing.netmx1.improvmx.commx2.improvmx.commx76.m2bp.commx76.mb1p.commxbackup.routing.netA159.69.8.194185.151.30.170188.166.40.4199.59.242.150199.59.242.1512a07:7800::170
NSnadia.ns.cloudflare.com2015-08-07 → 2017-01-06 · 4 obs
● 2015-08-07 02:04:24
● 2017-01-06 07:22:14
○ 2018-03-06 15:43:50
○ 2026-07-31 06:20:52
NSns.rcp.net.pe2026-02-15 → 2026-07-31 · 5 obs
○ 2021-11-13 17:39:26
● 2026-02-15 21:30:46
○ 2026-06-30 09:30:04
● 2026-07-28 12:42:44
● 2026-07-31 06:20:52
NSns1.bodis.com2018-03-06 → 2019-08-25 · 5 obs
○ 2017-01-06 07:22:14
● 2018-03-06 15:43:50
● 2019-08-25 12:33:46
○ 2020-03-21 15:44:04
○ 2026-07-31 06:20:52
NSns1.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
NSns1.stackdns.com2021-11-13 → 2021-11-13 · 4 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
○ 2026-02-15 21:30:46
○ 2026-07-31 06:20:52
NSns2.bodis.com2018-03-06 → 2019-08-25 · 5 obs
○ 2017-01-06 07:22:14
● 2018-03-06 15:43:50
● 2019-08-25 12:33:46
○ 2020-03-21 15:44:04
○ 2026-07-31 06:20:52
NSns2.rcp.net.pe2026-02-15 → 2026-07-31 · 5 obs
○ 2021-11-13 17:39:26
● 2026-02-15 21:30:46
○ 2026-06-30 09:30:04
● 2026-07-28 12:42:44
● 2026-07-31 06:20:52
NSns2.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
NSns2.stackdns.com2021-11-13 → 2021-11-13 · 4 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
○ 2026-02-15 21:30:46
○ 2026-07-31 06:20:52
NSns3.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
NSns3.stackdns.com2021-11-13 → 2021-11-13 · 4 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
○ 2026-02-15 21:30:46
○ 2026-07-31 06:20:52
NSns4.stackdns.com2021-11-13 → 2021-11-13 · 4 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
○ 2026-02-15 21:30:46
○ 2026-07-31 06:20:52
NStheo.ns.cloudflare.com2015-08-07 → 2017-01-06 · 4 obs
● 2015-08-07 02:04:24
● 2017-01-06 07:22:14
○ 2018-03-06 15:43:50
○ 2026-07-31 06:20:52
MXmx.stackmail.com2021-11-13 → 2026-02-15 · 5 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
● 2026-02-15 21:30:46
○ 2026-02-18 01:30:06
○ 2026-07-31 06:20:52
MXmx01.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
MXmx02.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
MXmx03.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
MXmx1.improvmx.com2015-08-07 → 2017-01-06 · 4 obs
● 2015-08-07 02:04:24
● 2017-01-06 07:22:14
○ 2018-03-06 15:43:50
○ 2026-07-31 06:20:52
MXmx2.improvmx.com2015-08-07 → 2017-01-06 · 4 obs
● 2015-08-07 02:04:24
● 2017-01-06 07:22:14
○ 2018-03-06 15:43:50
○ 2026-07-31 06:20:52
MXmx76.m2bp.com2018-03-06 → 2019-08-25 · 5 obs
○ 2017-01-06 07:22:14
● 2018-03-06 15:43:50
● 2019-08-25 12:33:46
○ 2020-03-21 15:44:04
○ 2026-07-31 06:20:52
MXmx76.mb1p.com2018-03-06 → 2019-08-25 · 5 obs
○ 2017-01-06 07:22:14
● 2018-03-06 15:43:50
● 2019-08-25 12:33:46
○ 2020-03-21 15:44:04
○ 2026-07-31 06:20:52
MXmxbackup.routing.net2020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
A159.69.8.1942020-03-21 → 2020-06-06 · 5 obs
○ 2019-08-25 12:33:46
● 2020-03-21 15:44:04
● 2020-06-06 00:26:54
○ 2021-11-13 17:39:26
○ 2026-07-31 06:20:52
A185.151.30.1702021-11-13 → 2026-02-15 · 5 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
● 2026-02-15 21:30:46
○ 2026-02-18 01:30:06
○ 2026-07-31 06:20:52
A188.166.40.42015-08-07 → 2017-01-06 · 4 obs
● 2015-08-07 02:04:24
● 2017-01-06 07:22:14
○ 2018-03-06 15:43:50
○ 2026-07-31 06:20:52
A199.59.242.1502018-03-06 → 2018-03-06 · 4 obs
○ 2017-01-06 07:22:14
● 2018-03-06 15:43:50
○ 2018-12-22 23:33:24
○ 2026-07-31 06:20:52
A199.59.242.1512018-12-22 → 2019-08-25 · 5 obs
○ 2018-03-06 15:43:50
● 2018-12-22 23:33:24
● 2019-08-25 12:33:46
○ 2020-03-21 15:44:04
○ 2026-07-31 06:20:52
A2a07:7800::1702021-11-13 → 2026-02-15 · 5 obs
○ 2020-06-06 00:26:54
● 2021-11-13 17:39:26
● 2026-02-15 21:30:46
○ 2026-02-18 01:30:06
○ 2026-07-31 06:20:52

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
pea.lactld.org, pch.rcp.pe, pe1.dnsnode.net, quipu.rcp.net.pe7 records
mx.pens2.rcp.net.pe, ns.rcp.net.pe-

✅ Authoritative Response

Server:209.45.127.3

NS records: ns2.rcp.net.pe, ns.rcp.net.pe

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mx.pe (unsigned zone)

⏱️ Timing

Total: 850ms | Queries: -

📄 Records

TypeCountSample Data
NS2NS.RCP.NET.pe, NS2.RCP.NET.pe
SOA1NS.RCP.NET.pe OPERADOR.RCP.pe

📌 Glue Records Collected

Total: 7

In-bailiwick: 3 (pch.rcp.pe, quipu.rcp.net.pe, pch.rcp.pe)

Out-of-bailiwick: 4 (a.lactld.org, pe1.dnsnode.net, a.lactld.org...)

Analysis

Name Servers

mx.pe has two authoritative name servers — ns2.rcp.net.pe and ns.rcp.net.pe.

mx.pe has the same name server delegation as a number of other domains, such as consejoprensaperuana.org.pe, cosegur.com.pe, eppoweb.pe and two more.

mx.pe has at least partial name server overlap with other domains, such as servimec.com.pe, cmp.net.pe, 3.45.209.in-addr.arpa and two others.

It is common to find these name servers paired with the name servers ichu.rcp.net.pe.

ns2.rcp.net.pe directs to 209.45.127.3 and ns.rcp.net.pe directs to 161.132.17.10; each host name points to exactly one IP number.