apiworking.pe - robtex.com
apiworking.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-02-23 #23 | ||||||
Up
consultaruc.apiworking.pe |
Same first word
apiworking.pe |
apiworking.co |
DNS History
13 records (11 active, 2 former)
●NSns-1492.awsdns-58.org2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●NSns-1592.awsdns-07.co.uk2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●NSns-398.awsdns-49.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●NSns-765.awsdns-31.net2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●MXalt1.aspmx.l.google.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●MXalt2.aspmx.l.google.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●MXalt3.aspmx.l.google.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●MXalt4.aspmx.l.google.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
●MXaspmx.l.google.com2026-02-15 → 2026-02-24 · 2 obs
● 2026-02-24 21:20:42
○A3.92.119.572026-02-15 → 2026-02-19 · 4 obs
● 2026-02-19 09:06:32
○ 2026-02-24 21:20:40
○ 2026-02-24 21:20:42
●A44.213.4.1392026-02-24 → 2026-02-24 · 3 obs
● 2026-02-24 21:20:40
● 2026-02-24 21:20:42
●A52.86.68.302026-02-24 → 2026-02-24 · 3 obs
● 2026-02-24 21:20:40
● 2026-02-24 21:20:42
○A98.89.231.792026-02-15 → 2026-02-19 · 4 obs
● 2026-02-19 09:06:32
○ 2026-02-24 21:20:40
○ 2026-02-24 21:20:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pe | quipu.rcp.net.pe, a.lactld.org, pch.rcp.pe, pe1.dnsnode.net | 7 records |
| apiworking.pe | ns-398.awsdns-49.com, ns-765.awsdns-31.net, ns-1592.awsdns-07.co.uk, ns-1492.awsdns-58.org | - |
✅ Authoritative Response
Server: 205.251.197.212
NS records: ns-398.awsdns-49.com, ns-765.awsdns-31.net, ns-1592.awsdns-07.co.uk, ns-1492.awsdns-58.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for apiworking.pe (unsigned zone)
⏱️ Timing
Total: 1021ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.86.68.30, 44.213.4.139 |
| NS | 4 | ns-1492.awsdns-58.org, ns-1592.awsdns-07.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=xqFK8M2W5Hqi29A, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-1492.awsdns-58.org awsdns-hostmaster. |
📌 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...)
AI analysis
The parent of consultaruc.apiworking.pe is apiworking.pe.
apiworking.pe points to two IP numbers: 44.213.4.139 and 52.86.68.30.
Other host names, for instance ec2-44-213-4-139.compute-1.amazonaws.com, share IP numbers with apiworking.pe.
apiworking.pe is delegated to four name servers: ns-398.awsdns-49.com, ns-765.awsdns-31.net, ns-1492.awsdns-58.org and ns-1592.awsdns-07.co.uk.
apiworking.pe shares name servers with other domains at least partially, for instance mcmichaelfuneralhome.com, phanarts.com, businessmessenger.com, telium.io and stvp.stanford.edu.
These name servers are commonly used with ns-840.awsdns-41.net, ns-1197.awsdns-21.org, ns-1850.awsdns-39.co.uk, ns-2044.awsdns-63.co.uk, ns-904.awsdns-49.net and ns-1327.awsdns-37.org.
Host names with two IP numbers:
ns-398.awsdns-49.com resolves to 2600:9000:5301:8e00::1 and 205.251.193.142.
ns-765.awsdns-31.net resolves to 2600:9000:5302:fd00::1 and 205.251.194.253.
ns-1492.awsdns-58.org resolves to 2600:9000:5305:d400::1 and 205.251.197.212.
ns-1592.awsdns-07.co.uk resolves to 2600:9000:5306:3800::1 and 205.251.198.56.
apiworking.pe is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
apiworking.pe shares some mail servers with other domains, including ns500742.ns500754.ns500742.ns500754.ns500754.ns500742.ns500742.ns500678.ns500688.ns500678.ns500666.ns500666.ns500291.ns500131.lustychickser.com, ns500742.ns500742.ns500754.ns500671.ns500754.ns500754.ns500704.ns500705.ns500704.ns500649.ns500649.ns500649.lustychickser.com, ns500698.ns500759.ns500759.ns500758.ns500759.ns500698.ns500698.ns500735.ns500735.ns500708.ns500698.ns500686.ns500686.ns500576.ns500619.trackreceptor.com, ns500759.ns500759.ns500735.ns500698.ns500698.ns500736.ns500698.ns500698.ns500698.ns500698.ns500619.ns500619.trackreceptor.com and ns500759.ns500698.ns500736.ns500735.ns500698.ns500735.ns500736.ns500736.ns500698.ns500698.ns500708.ns500619.ns500619.ns500652.ns500576.trackreceptor.com.
these mail servers are commonly used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27.