ipnetwork.com.pe - dns.ninja
ipnetwork.com.pe
| DNSSEC | ⚠️ Not signed | ||||||
| A | 161.132.57.199🇵🇪 AS3132161.132.57.0/24 | ||||||
| PTR | yl-pachacamac.yachay.pe | ||||||
| NS | ns2.rcp.net.pe ⭐ | ||||||
| A | 209.45.127.3🇵🇪 AS3132209.45.127.0/24 SP-RCP | ||||||
| PTR | ichu.rcp.net.pe | ||||||
| NS | ns.rcp.net.pe | ||||||
| A | 161.132.17.10🇵🇪 AS3132161.132.17.0/24 PNAP-SEF wowtech-1 | ||||||
| MX | ipnetwork.com.pe ⭐ | ||||||
| A | 161.132.57.199🇵🇪 AS3132161.132.57.0/24 | ||||||
| PTR | yl-pachacamac.yachay.pe | ||||||
| TXT | v=spf1 +a +mx +ip4:161.132.57.199 +ip4:161.132.19.0/24 +ip4:209.45.69.0/24 +i... | ||||||
| SOA | ns.rcp.net.peoperador@rcp.pe 2024-08-27 #2 | ||||||
com.pe
| DNSSEC | ⚠️ Not signed | ||||||
| NS | quipu.rcp.net.pe ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a.lactld.org ⚠️ Not in parent delegation | ||||||
| NS | pch.rcp.pe ⚠️ Not in parent delegation | ||||||
| NS | pe1.dnsnode.net ⚠️ Not in parent delegation | ||||||
| SOA | quipu.rcp.net.peoperador@rcp.pe 2026-07-28 #9 | ||||||
MX for
ipnetwork.com.pe |
Same first word
Similar names
DNS History
6 records (4 active, 2 former)
●NSns.rcp.net.pe2017-02-06 → 2026-07-28 · 2 obs
● 2026-07-28 15:05:34
●NSns2.rcp.net.pe2017-02-06 → 2026-07-28 · 2 obs
● 2026-07-28 15:05:34
●MXipnetwork.com.pe2017-02-06 → 2026-07-28 · 2 obs
● 2026-07-28 15:05:34
○A161.132.18.2512018-10-27 → 2018-10-27 · 4 obs
● 2018-10-27 12:23:50
○ 2026-02-18 22:34:22
○ 2026-07-28 15:05:34
●A161.132.57.1992026-02-18 → 2026-07-28 · 3 obs
● 2026-02-18 22:34:22
● 2026-07-28 15:05:34
○A209.45.69.1122017-02-06 → 2017-02-06 · 3 obs
○ 2018-10-27 12:23:50
○ 2026-07-28 15:05:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pe | a.lactld.org, pch.rcp.pe, pe1.dnsnode.net, quipu.rcp.net.pe | 7 records |
| ipnetwork.com.pe | ns2.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 ipnetwork.com.pe (unsigned zone)
⏱️ Timing
Total: 1747ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 161.132.57.199 |
| NS | 2 | NS2.RCP.NET.pe, NS.RCP.NET.pe |
| MX | 1 | ipnetwork.com.pe (pri: 0) |
| TXT | 1 | v=spf1 +a +mx +ip4:161.132.57.199 +ip4:1 |
| SOA | 1 | ns.rcp.net.pe operador.rcp.pe |
📌 Glue Records Collected
Total: 7
In-bailiwick: 3 (pch.rcp.pe, pch.rcp.pe, quipu.rcp.net.pe)
Out-of-bailiwick: 4 (a.lactld.org, a.lactld.org, pe1.dnsnode.net...)
Analysis
Mail Server Role
ipnetwork.com.pe is listed as a mail server for itself.
IP Addresses
ipnetwork.com.pe resolves to one IP address: 161.132.57.199.
mayday.pe, sgatel.com.pe, celda.com.pe and two other host names share IP numbers with ipnetwork.com.pe.
Name Servers
ipnetwork.com.pe uses two name servers for its delegation: ns2.rcp.net.pe and ns.rcp.net.pe.
ipnetwork.com.pe uses the same name servers as several other domains — among them proiron.pe, cacbolognesi.com.pe, protemax.com.pe and two more.
The name servers of ipnetwork.com.pe overlap at least partially with those of other domains — among them sbc.com.pe, 215.132.161.in-addr.arpa, 105.132.161.in-addr.arpa and two more.
These name servers commonly appear in combination with the name servers ichu.rcp.net.pe.
Both ns2.rcp.net.pe and ns.rcp.net.pe have a single IP address each — ns2.rcp.net.pe resolves to 209.45.127.3 while ns.rcp.net.pe resolves to 161.132.17.10.
Mail Servers
Mail for ipnetwork.com.pe is handled by one mail server — ipnetwork.com.pe.
ipnetwork.com.pe directs to just one IP number, 161.132.57.199.