partnercap.com - dns.ninja

`partnercap.com`

DNSSEC	⚠️ Not signed
A	157.173.209.142^{🇬🇧 IIHOS001157.173.208.0/21}
NS	`dns101.register.com` ⭐
		A	162.159.24.117^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`dns102.register.com`
		A	162.159.25.158^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`partnercap-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c801::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr02cu00200.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:f802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00202.inbound.protection.outlook.com`
		A	52.101.9.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.40.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr03cu00204.inbound.protection.outlook.com`
		A	52.101.41.58^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr02cu00102.inbound.protection.outlook.com`
		A	52.101.194.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
TXT	`MS=ms98644181`
TXT	`v=spf1 include:edgepilot.com -all`
SOA	`DNS101.REGISTER.com`root@REGISTER.com serial=126061709

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1785396777

Same first word

partnercap.com

Similar names

pacpartner.com

partnerpac.com

cpapartner.ru

cappartner.com

partnercpa.com

parentcrap.com

cpapartner.com

partnercpa.fun

cappartner.eu

DNS History

14 records (4 active, 10 former)

○NSdns073.a.register.com2015-08-04 → 2020-01-27 · 4 obs

● 2015-08-04 11:22:18
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

●NSdns101.register.com2026-03-08 → 2026-07-30 · 3 obs

○ 2020-01-27 22:56:16
● 2026-03-08 03:59:44
● 2026-07-30 07:42:16

●NSdns102.register.com2026-03-08 → 2026-07-30 · 3 obs

○ 2020-01-27 22:56:16
● 2026-03-08 03:59:44
● 2026-07-30 07:42:16

○NSdns201.b.register.com2015-08-04 → 2020-01-27 · 4 obs

● 2015-08-04 11:22:18
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

○NSdns229.c.register.com2015-08-04 → 2020-01-27 · 4 obs

● 2015-08-04 11:22:18
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

○NSdns249.d.register.com2015-08-04 → 2020-01-27 · 4 obs

● 2015-08-04 11:22:18
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

●MXpartnercap-com.mail.protection.outlook.com2020-01-27 → 2026-07-30 · 3 obs

○ 2017-03-28 01:55:44
● 2020-01-27 22:56:16
● 2026-07-30 07:42:16

○MXserver4.inboundmx.com2015-08-04 → 2017-03-28 · 4 obs

● 2015-08-04 11:22:18
● 2017-03-28 01:55:44
○ 2020-01-27 22:56:16
○ 2026-07-30 07:42:16

○MXserver5.inboundmx.com2015-08-04 → 2017-03-28 · 4 obs

● 2015-08-04 11:22:18
● 2017-03-28 01:55:44
○ 2020-01-27 22:56:16
○ 2026-07-30 07:42:16

●A157.173.209.1422026-03-08 → 2026-07-30 · 3 obs

○ 2020-01-27 22:56:16
● 2026-03-08 03:59:44
● 2026-07-30 07:42:16

○A199.85.91.112017-03-28 → 2017-03-28 · 4 obs

○ 2016-07-14 03:05:14
● 2017-03-28 01:55:44
○ 2020-01-27 22:56:16
○ 2026-07-30 07:42:16

○A54.164.9.1072020-01-27 → 2020-01-27 · 4 obs

○ 2017-03-28 01:55:44
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

○A54.85.200.1312020-01-27 → 2020-01-27 · 4 obs

○ 2017-03-28 01:55:44
● 2020-01-27 22:56:16
○ 2026-03-08 03:59:44
○ 2026-07-30 07:42:16

○A69.89.67.2312015-08-04 → 2016-07-14 · 4 obs

● 2015-08-04 11:22:18
● 2016-07-14 03:05:14
○ 2017-03-28 01:55:44
○ 2026-07-30 07:42:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net...	-
partnercap.com	dns101.register.com, dns102.register.com	2 records

✅ Authoritative Response

Server:162.159.24.117

NS records: dns101.register.com, dns102.register.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for partnercap.com (unsigned zone)

⏱️ Timing

Total: 212ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`157.173.209.142`
NS	2	`dns102.register.com, dns101.register.com`
MX	1	`partnercap-com.mail.protection.outlook.c`
TXT	2	`v=spf1 include:edgepilot.com -all, MS=ms98644181`
SOA	1	`DNS101.REGISTER.com root.REGISTER.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns101.register.com, dns102.register.com)

Analysis

IP Addresses

partnercap.com has exactly one IP address — 157.173.209.142.

partnercap.com shares its IP numbers with other host names like pacocean.net, jpcus.com and letsrandevu.com.

Name Servers

partnercap.com is served by two delegated name servers, dns101.register.com and dns102.register.com.

The name server configuration of partnercap.com is shared with other domains, for instance senioritees.com, shanghaijockeyclub.com, abidingfaith-umc.org and two others.

dns101.register.com directs to 162.159.24.117 and dns102.register.com directs to 162.159.25.158; each host name points to exactly one IP number.

Mail Servers

partnercap.com uses one mail server — partnercap-com.mail.protection.outlook.com.

partnercap-com.mail.protection.outlook.com has 8 IP addresses: 52.101.9.17, 52.101.40.4, 52.101.41.58 plus 5 more.