apto.pe - robtex.com
apto.pe
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns01.dns.nexus ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:ab8🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.10.184Cloudflare162.159.10.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns02.dns.nexus | ||||||
| A | 2400:cb00:2049:1::a29f:8ba🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.8.186Cloudflare162.159.8.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns01.dns.nexusit@apto.pe 2026-06-20 #1 | ||||||
pe
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | quipu.rcp.net.pe ⭐ | ||||||
| NS | a.lactld.org ⚠️ Not in parent delegation | ||||||
| NS | pch.rcp.pe | ||||||
| NS | pe1.dnsnode.net ⚠️ Not in parent delegation | ||||||
| SOA | quipu.rcp.net.peoperador@rcp.pe 2026-07-05 #0 | ||||||
PTR for
Same first word
Similar names
DNS History
12 records (2 active, 10 former)
○NSns.rcp.net.pe2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
●NSns01.dns.nexus2026-07-02 → 2026-07-05 · 3 obs
● 2026-07-02 03:32:26
● 2026-07-05 07:13:24
●NSns02.dns.nexus2026-07-02 → 2026-07-05 · 3 obs
● 2026-07-02 03:32:26
● 2026-07-05 07:13:24
○NSns2.rcp.net.pe2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXalt1.aspmx.l.google.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXalt2.aspmx.l.google.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXaspmx.l.google.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXaspmx2.googlemail.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXaspmx3.googlemail.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXaspmx4.googlemail.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○MXaspmx5.googlemail.com2015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
○A192.211.58.682015-07-26 → 2017-08-06 · 4 obs
● 2017-08-06 17:40:16
○ 2026-07-02 03:32:26
○ 2026-07-05 07:13:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pe | a.lactld.org, pe1.dnsnode.net, pch.rcp.pe, quipu.rcp.net.pe | 7 records |
| apto.pe | ns02.dns.nexus, ns01.dns.nexus | - |
✅ Authoritative Response
Server:162.159.10.184
NS records: ns02.dns.nexus, ns01.dns.nexus
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for apto.pe (unsigned zone)
⏱️ Timing
Total: 663ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns01.dns.nexus, ns02.dns.nexus |
| SOA | 1 | ns01.dns.nexus it.apto.pe |
📌 Glue Records Collected
Total: 7
In-bailiwick: 3 (quipu.rcp.net.pe, pch.rcp.pe, pch.rcp.pe)
Out-of-bailiwick: 4 (pe1.dnsnode.net, a.lactld.org, pe1.dnsnode.net...)
Analysis
Name Servers
apto.pe has two authoritative name servers — ns01.dns.nexus and ns02.dns.nexus.
apto.pe has the same name server delegation as a number of other domains, such as h1.pe, enlteamperu.com, freihe.it and two more.
The name servers for apto.pe overlap at least partially with those of other domains — for example frontman.sh.
Both ns01.dns.nexus and ns02.dns.nexus have two IP addresses each. ns01.dns.nexus resolves to 162.159.10.184 and 2400:cb00:2049:1::a29f:ab8; ns02.dns.nexus resolves to 162.159.8.186 and 2400:cb00:2049:1::a29f:8ba.