`parispartner.com`

DNSSEC	⚠️ Not signed
A	92.154.90.59^{🇫🇷 AS321592.154.0.0/17 France Telecom Orange}
		PTR	`laubervilliers-657-1-83-59.w92-154.abo.wanadoo.fr`
NS	`ns1.validname.com` ⭐
		A	2001:4ba0:cafe:532::1^{🇩🇪 MYLOC-AS2001:4ba0::/32 myLoc managed IT AG}
			PTR	`dnssec1.namebay.com`
		A	2a01:c8:ff00:201::133^{🇫🇷 NAMESHIELD2a01:c8:ff00::/40 Global IPv6 route to Namebay}
		A	62.141.38.216^{🇩🇪 MYLOC-AS62.141.32.0/20 myLoc managed IT AG}
			PTR	`smtp12.validname.com`
		A	185.65.56.133^{🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap}
			PTR	`dns1.namebay.com`
NS	`ns2.validname.com`
		A	2001:41d0:203:ddee::34^{🇫🇷 OVH2001:41d0::/32 IPv6}
			PTR	`ns2.namebay.com`
		A	2a01:c8:ff00:201::134^{🇫🇷 NAMESHIELD2a01:c8:ff00::/40 Global IPv6 route to Namebay}
		A	91.134.185.34^{🇫🇷 OVH91.134.0.0/16}
			PTR	`dns4.namebay.com`
		A	185.65.56.134^{🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap}
			PTR	`dns2.namebay.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c0b::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dd-in-f26.1e100.net`
		A	74.125.137.26^{🇺🇸 Google74.125.137.0/24}
			PTR	`dy-in-f26.1e100.net`
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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`google-site-verification=5TB95aqNbL4ji1EZLaRVB5tUQ32vp1q-0fT71JSXnq0`
SOA	`ns1.validname.com`admin@validname.com 2026-03-21 #0

`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=1775951787

Same first word

parispartner.com

parispartner.jp

Similar names

paripartners.ru

DNS History

9 records (6 active, 3 former)

●NSns1.validname.com2008-03-19 → 2026-04-12 · 2 obs

● 2008-03-19 03:44:26
● 2026-04-12 00:19:06

●NSns2.validname.com2008-03-19 → 2026-04-12 · 2 obs

● 2008-03-19 03:44:26
● 2026-04-12 00:19:06

●MXalt1.aspmx.l.google.com2017-04-18 → 2026-04-12 · 3 obs

○ 2015-12-16 16:50:00
● 2017-04-18 21:42:36
● 2026-04-12 00:19:06

●MXalt2.aspmx.l.google.com2017-04-18 → 2026-04-12 · 3 obs

○ 2015-12-16 16:50:00
● 2017-04-18 21:42:36
● 2026-04-12 00:19:06

●MXaspmx.l.google.com2017-04-18 → 2026-04-12 · 3 obs

○ 2015-12-16 16:50:00
● 2017-04-18 21:42:36
● 2026-04-12 00:19:06

○MXmail.parispartner.com2008-03-19 → 2015-08-12 · 4 obs

● 2008-03-19 03:44:26
● 2015-08-12 11:21:54
○ 2015-12-16 16:50:00
○ 2026-04-12 00:19:06

○A82.227.136.2302015-08-12 → 2016-08-13 · 5 obs

○ 2008-03-19 03:44:26
● 2015-08-12 11:21:54
● 2016-08-13 01:13:58
○ 2017-04-18 21:42:36
○ 2026-04-12 00:19:06

○A92.154.5.1192017-04-18 → 2017-04-18 · 4 obs

○ 2016-08-13 01:13:58
● 2017-04-18 21:42:36
○ 2026-03-27 08:41:44
○ 2026-04-12 00:19:06

●A92.154.90.592026-03-27 → 2026-04-12 · 3 obs

○ 2017-04-18 21:42:36
● 2026-03-27 08:41:44
● 2026-04-12 00:19:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
parispartner.com	ns1.validname.com, ns2.validname.com	8 records

✅ Authoritative Response

Server:185.65.56.133

NS records: ns1.validname.com, ns2.validname.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for parispartner.com (unsigned zone)

⏱️ Timing

Total: 365ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`92.154.90.59`
NS	2	`ns2.validname.com, ns1.validname.com`
MX	3	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`google-site-verification=5TB95aqNbL4ji1E`
SOA	1	`ns1.validname.com admin.validname.com`