applying.pe - dns.ninja

`applying.pe`

DNSSEC	⚠️ Not signed
NS	`ns-758.awsdns-30.net` ⭐
		A	2600:9000:5302:f600::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-758.awsdns-30.net`
		A	205.251.194.246^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-758.awsdns-30.net`
NS	`ns-1133.awsdns-13.org`
		A	2600:9000:5304:6d00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1133.awsdns-13.org`
		A	205.251.196.109^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1133.awsdns-13.org`
NS	`ns-1772.awsdns-29.co.uk`
		A	2600:9000:5306:ec00::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1772.awsdns-29.co.uk`
		A	205.251.198.236^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1772.awsdns-29.co.uk`
NS	`ns-436.awsdns-54.com`
		A	2600:9000:5301:b400::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-436.awsdns-54.com`
		A	205.251.193.180^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-436.awsdns-54.com`
MX	`applying-pe.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01703.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr05cu00501.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00404.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.10.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00204.inbound.protection.outlook.com`
		A	52.101.10.16^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn6pr21cu00500.inbound.protection.outlook.com`
		A	52.101.42.16^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr05cu00300.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns-758.awsdns-30.net`awsdns-hostmaster@amazon.com serial=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 #18

Same first word

applying.com.au

applying.ca

applying.online

applying.cl

applying.de

applying.cloud

applying.pe

applying.com

applying.net

applying.it

Similar names

pingplay.com

appingly.com

pingplay.me

yappling.com

playping.com

DNS History

22 records (5 active, 17 former)

●NSns-1133.awsdns-13.org2026-04-28 → 2026-07-28 · 3 obs

○ 2016-04-27 02:58:18
● 2026-04-28 00:59:40
● 2026-07-28 01:29:14

○NSns-1306.awsdns-35.org2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○NSns-1614.awsdns-09.co.uk2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

●NSns-1772.awsdns-29.co.uk2026-04-28 → 2026-07-28 · 3 obs

○ 2016-04-27 02:58:18
● 2026-04-28 00:59:40
● 2026-07-28 01:29:14

●NSns-436.awsdns-54.com2026-04-28 → 2026-07-28 · 3 obs

○ 2016-04-27 02:58:18
● 2026-04-28 00:59:40
● 2026-07-28 01:29:14

○NSns-72.awsdns-09.com2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

●NSns-758.awsdns-30.net2026-04-28 → 2026-07-28 · 3 obs

○ 2016-04-27 02:58:18
● 2026-04-28 00:59:40
● 2026-07-28 01:29:14

○NSns-823.awsdns-38.net2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○NSns1.siteground195.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○NSns2.siteground195.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○MXalt1.aspmx.l.google.com2015-07-24 → 2016-04-27 · 4 obs

● 2015-07-24 01:08:34
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○MXalt2.aspmx.l.google.com2015-07-24 → 2016-04-27 · 4 obs

● 2015-07-24 01:08:34
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○MXalt3.aspmx.l.google.com2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○MXalt4.aspmx.l.google.com2016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

●MXapplying-pe.mail.protection.outlook.com2026-04-28 → 2026-07-28 · 3 obs

○ 2016-04-27 02:58:18
● 2026-04-28 00:59:40
● 2026-07-28 01:29:14

○MXaspmx.l.google.com2015-07-24 → 2016-04-27 · 4 obs

● 2015-07-24 01:08:34
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

○MXaspmx2.googlemail.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○MXaspmx3.googlemail.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○MXaspmx4.googlemail.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○MXaspmx5.googlemail.com2015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○A181.224.138.1212015-07-24 → 2016-02-08 · 4 obs

● 2015-07-24 01:08:34
● 2016-02-08 20:03:30
○ 2016-04-27 02:58:18
○ 2026-07-28 01:29:14

○A54.149.222.732016-04-27 → 2016-04-27 · 4 obs

○ 2016-02-08 20:03:30
● 2016-04-27 02:58:18
○ 2026-04-28 00:59:40
○ 2026-07-28 01:29:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pe	quipu.rcp.net.pe, pe1.dnsnode.net, a.lactld.org, pch.rcp.pe	7 records
applying.pe	ns-1772.awsdns-29.co.uk, ns-758.awsdns-30.net, ns-436.awsdns-54.com, ns-1133.awsdns-13.org	-

✅ Authoritative Response

Server:205.251.196.109

NS records: ns-1772.awsdns-29.co.uk, ns-758.awsdns-30.net, ns-436.awsdns-54.com, ns-1133.awsdns-13.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for applying.pe (unsigned zone)

⏱️ Timing

Total: 335ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1133.awsdns-13.org, ns-1772.awsdns-29.co.uk...`
MX	1	`applying-pe.mail.protection.outlook.com`
TXT	1	`v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns-758.awsdns-30.net awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 7

In-bailiwick: 3 (pch.rcp.pe, quipu.rcp.net.pe, pch.rcp.pe)

Out-of-bailiwick: 4 (pe1.dnsnode.net, a.lactld.org, pe1.dnsnode.net...)

Analysis

Name Servers

The NS records for applying.pe point to four name servers: ns-436.awsdns-54.com, ns-758.awsdns-30.net, ns-1133.awsdns-13.org and ns-1772.awsdns-29.co.uk.

The name servers of applying.pe overlap at least partially with those of other domains — among them myantisocial.net, dimpleindustries.com, email.pens.com and two more.

Each of the four hosts ns-436.awsdns-54.com, ns-758.awsdns-30.net, ns-1133.awsdns-13.org and ns-1772.awsdns-29.co.uk has two IP addresses. ns-436.awsdns-54.com points to 205.251.193.180 and 2600:9000:5301:b400::1. ns-758.awsdns-30.net points to 205.251.194.246 and 2600:9000:5302:f600::1. ns-1133.awsdns-13.org points to 205.251.196.109 and 2600:9000:5304:6d00::1. ns-1772.awsdns-29.co.uk points to 205.251.198.236 and 2600:9000:5306:ec00::1.

Mail Servers

The sole mail server for applying.pe is applying-pe.mail.protection.outlook.com.

With 8 IP addresses total, applying-pe.mail.protection.outlook.com resolves to 52.101.9.0, 52.101.10.12, 52.101.10.16 and 5 others.