random.pe - dns.ninja
random.pe
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-08-07 #22 | ||||||
PTR for
Same first word
Similar names
DNS History
12 records (9 active, 3 former)
●NSns1.digitalocean.com2026-03-03 → 2026-08-08 · 3 obs
● 2026-03-03 03:27:52
● 2026-08-08 04:52:36
○NSns1.mediatemple.net2017-09-09 → 2017-09-09 · 3 obs
○ 2026-03-03 03:27:52
○ 2026-08-08 04:52:36
●NSns2.digitalocean.com2026-03-03 → 2026-08-08 · 3 obs
● 2026-03-03 03:27:52
● 2026-08-08 04:52:36
○NSns2.mediatemple.net2017-09-09 → 2017-09-09 · 3 obs
○ 2026-03-03 03:27:52
○ 2026-08-08 04:52:36
●NSns3.digitalocean.com2026-03-03 → 2026-08-08 · 3 obs
● 2026-03-03 03:27:52
● 2026-08-08 04:52:36
●MXalt1.aspmx.l.google.com2017-09-09 → 2026-08-08 · 2 obs
● 2026-08-08 04:52:36
●MXalt2.aspmx.l.google.com2017-09-09 → 2026-08-08 · 2 obs
● 2026-08-08 04:52:36
●MXalt3.aspmx.l.google.com2017-09-09 → 2026-08-08 · 2 obs
● 2026-08-08 04:52:36
●MXalt4.aspmx.l.google.com2017-09-09 → 2026-08-08 · 2 obs
● 2026-08-08 04:52:36
●MXaspmx.l.google.com2017-09-09 → 2026-08-08 · 2 obs
● 2026-08-08 04:52:36
●A165.227.95.2192026-03-03 → 2026-08-08 · 3 obs
● 2026-03-03 03:27:52
● 2026-08-08 04:52:36
○A216.70.112.1582017-09-09 → 2017-09-09 · 3 obs
○ 2026-03-03 03:27:52
○ 2026-08-08 04:52:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pe | pch.rcp.pe, quipu.rcp.net.pe | - |
| random.pe | ns3.digitalocean.com, ns1.digitalocean.com, ns2.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.49.209
NS records: ns3.digitalocean.com, ns1.digitalocean.com, ns2.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for random.pe (unsigned zone)
⏱️ Timing
Total: 518ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 165.227.95.219 |
| NS | 3 | ns2.digitalocean.com, ns3.digitalocean.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns1.digitalocean.com hostmaster.random.p |
Analysis
IP Addresses
random.pe has exactly one IP address — 165.227.95.219.
Name Servers
The authoritative name servers for random.pe are ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com — three in total.
There is at least partial name server overlap between random.pe and other domains — 1.0.0.4.0.2.8.0.0.0.0.0.0.0.0.0.0.d.0.0.2.0.0.0.0.8.8.a.4.0.6.2.ip6.arpa, melonloans.com, i-translate.info and two more among them.
ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com all resolve to exactly two IP numbers apiece: ns1.digitalocean.com → 172.64.52.210 and 2606:4700:52::ac40:34d2; ns2.digitalocean.com → 172.64.53.21 and 2606:4700:5a::ac40:3515; ns3.digitalocean.com → 172.64.49.209 and 2606:4700:52::ac40:31d1.
Mail Servers
Five mail servers handle random.pe: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by random.pe are shared with other domains: git-solutions.com.mx, awake-mode.com, wegoluck.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 172.253.62.27 and 2607:f8b0:4004:c17::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.