`idom.pe`

DNSSEC	⚠️ Not signed
A	68.183.154.24^{🇺🇸 DIGITALOCEAN68.183.144.0/20 DigitalOcean}
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}
			PTR	`ns.rcp.net.pe`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
MX	`alt1.aspmx.l.google.com`⁽²⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽³⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽⁴⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx4.googlemail.com`⁽⁶⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`aspmx5.googlemail.com`⁽⁷⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=eQrcLO-PahbapUfyR6AzW0Ly-3kW-_RPXEVQ9rxvE84`
SOA	`NS.RCP.NET.pe`OPERADOR@RCP.pe 2024-08-16 #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.pe`operador@rcp.pe 2026-07-27 #17

Same first word

idom.pe

idom.com.br

idom.com.ar

idom.cloud

idom.me

idom.net.ua

idom.net

idom.org

idom.ru

idom.es

idom.kr

idom.ca

idom.md

idom.pro

idom.cz

idom.fr

idom.online

idom.kz

idom.co.nz

idom.mobi

idom.ua

idom.tv

idom.com.pl

idom.de

idom.net.pl

idom.az

idom.by

idom.pl

idom.nl

idom.cn

idom.hu

idom.com

idom.mx

idom.su

idom.com.au

idom.bg

Similar names

domi.al

miod.co

modi.cn

mido.pro

imod.club

dimo.me

imdo.ro

omid.nu

iodm.co.uk

imdo.org

domi.kz

miod.com.au

mdoi.fr

imod.com.au

modi.de

mido.es

dimo.com.br

domi.codes

modi.tv

mido.co.th

moid.org

miod.bialystok.pl

mido.ws

dimo.com.ar

dmio.ru

mido.de

dimo.ws

mido.ar

dimo.co.id

dimo.org

omid.net

modi.cz

mdio.net

dimo.co

miod.org

dmoi.fr

imod.org.tr

mido.it

dimo.no

domi.(0x787878)

mido.swiss

imod.de

modi.ru

domi.org

imod.org

imdo.de

odim.fr

imdo.co

omid.es

omid.com.au

domi.bg

modi.uk

mido.ch

mido.sa

modi.media

mido.sg

miod.net

omid.ch

domi.cn

dimo.pt

domi.ca

iodm.net

omid.biz

domi.kg

domi.co

domi.org.cn

miod.com.ua

imod.eu

doim.de

imod.com.br

dimo.kr

imod.it

diom.si

odim.com

dimo.bg

diom.net

odim.org

diom.eu

omid.tv

domi.org.vn

dmoi.net

miod.cz

omid.az

moid.pl

iodm.biz

omid.one

mido.shop

mido.lu

miod.pl

modi.guru

domi.group

mido.fan

imod.in

mido.me

imod.se

DNS History

14 records (10 active, 4 former)

○NShuandoy.tdp.net.pe2008-10-24 → 2016-06-06 · 4 obs

● 2008-10-24 01:56:28
● 2016-06-06 03:32:32
○ 2017-03-25 20:32:08
○ 2026-07-27 23:25:34

○NShuascaran.tdp.net.pe2008-10-24 → 2016-06-06 · 4 obs

● 2008-10-24 01:56:28
● 2016-06-06 03:32:32
○ 2017-03-25 20:32:08
○ 2026-07-27 23:25:34

●NSns.rcp.net.pe2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●NSns2.rcp.net.pe2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXalt1.aspmx.l.google.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXalt2.aspmx.l.google.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXaspmx.l.google.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXaspmx2.googlemail.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXaspmx3.googlemail.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXaspmx4.googlemail.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

●MXaspmx5.googlemail.com2026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

○MXmail.idom.pe2008-10-24 → 2016-06-06 · 4 obs

● 2008-10-24 01:56:28
● 2016-06-06 03:32:32
○ 2017-03-25 20:32:08
○ 2026-07-27 23:25:34

○A200.121.170.412008-10-24 → 2016-06-06 · 4 obs

● 2008-10-24 01:56:28
● 2016-06-06 03:32:32
○ 2017-03-25 20:32:08
○ 2026-07-27 23:25:34

●A68.183.154.242026-06-30 → 2026-07-27 · 3 obs

○ 2017-03-25 20:32:08
● 2026-06-30 00:03:42
● 2026-07-27 23:25:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pe	a.lactld.org, pch.rcp.pe, pe1.dnsnode.net, quipu.rcp.net.pe	7 records
idom.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 idom.pe (unsigned zone)

⏱️ Timing

Total: 959ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`68.183.154.24`
NS	2	`NS2.RCP.NET.pe, NS.RCP.NET.pe`
MX	7	`ASPMX4.GOOGLEMAIL.COM (pri: 6), ALT2.ASPMX.L.GOOGLE.COM (pri: 3)...`
TXT	1	`google-site-verification=eQrcLO-PahbapUf`
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

IP Addresses

idom.pe resolves to just one IP address, 68.183.154.24.

Name Servers

idom.pe uses two name servers for its delegation: ns2.rcp.net.pe and ns.rcp.net.pe.

idom.pe shares its NS records with other domains, for example basambientales.com.pe, bicentenario.gob.pe, tlmperu.com.pe and two others.

idom.pe shares at least some of its name servers with other domains, including casuarinas.pe, 221.132.161.in-addr.arpa, 8.132.161.in-addr.arpa and two others.

These name servers are frequently seen alongside the name servers ichu.rcp.net.pe.

ns2.rcp.net.pe and ns.rcp.net.pe each resolve to one IP number: ns2.rcp.net.pe points to 209.45.127.3 and ns.rcp.net.pe points to 161.132.17.10.

Mail Servers

idom.pe is handled by 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.

There is at least a partial MX overlap between idom.pe and other domains, including trendero.com, culturachocolate.com, biznode.net and two others.

These mail servers tend to appear in combination with mail servers aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

aspmx4.googlemail.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.

aspmx.l.google.com directs traffic to 142.251.167.27 and 2607:f8b0:4004:c1d::1b.

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.26 and 2a00:1450:400b:c02::1a.

Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.