planogy.com - robtex.com

Search for stuff

`planogy.com`

DNSSEC	⚠️ Not signed
A	198.49.23.144^{🇺🇸 AS53831}
A	198.49.23.145^{🇺🇸 AS53831}
A	198.185.159.144^{🇺🇸 AS53831}
A	198.185.159.145^{🇺🇸 AS53831}
NS	`ns-cloud-b1.googledomains.com` ⭐
		A	2001:4860:4802:32::6b^{🇺🇸 Google}
		A	216.239.32.107^{🇺🇸 Google}
NS	`ns-cloud-b2.googledomains.com`
		A	2001:4860:4802:34::6b^{🇺🇸 Google}
		A	216.239.34.107^{🇺🇸 Google}
NS	`ns-cloud-b3.googledomains.com`
		A	2001:4860:4802:36::6b^{🇺🇸 Google}
		A	216.239.36.107^{🇺🇸 Google}
NS	`ns-cloud-b4.googledomains.com`
		A	2001:4860:4802:38::6b^{🇺🇸 Google}
		A	216.239.38.107^{🇺🇸 Google}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google}
		A	142.251.167.26^{🇺🇸 Google}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google}
		A	172.253.116.27^{🇺🇸 Google}
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google}
		A	192.178.223.26^{🇺🇸 Google}
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾

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

Up

www.planogy.com

Starts with same word

planogy.com

Starts similarily

npgoyal.com

lognpay.com

gonplay.com

playngo.net

plnyoga.blogspot.com

playngo.co

longpay.org

planygo.com

playngo.se

playong.com

playgon.com

paylong.com

pognaly.ru

lngopay.com

planogy.com

playngo.com

nlpyoga.com

pangoly.com

goplany.net

anglopy.com

playngo.casino

playngo.uk

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
planogy.com	ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com	8 records

✅ Authoritative Response

Server: 192.55.83.30

NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for planogy.com (unsigned zone)

⏱️ Timing

Total: 155ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`198.49.23.144, 198.185.159.145...`
NS	4	`ns-cloud-b1.googledomains.com, ns-cloud-b3.googledomains.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt4.aspmx.l.google.com (pri: 10)...`
TXT	1	`google-site-verification=Lob20C0WXZdCrTc`
HTTPS	1	`{"priority":1,"target":".","alpn":["h2",`
SOA	1	`ns-cloud-b1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)

AI analysis

planogy.com is a parent of www.planogy.com.

planogy.com resolves to four IPs: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.

Other host names such as emma.net, palaciodelosjugos.com, tk-ci.com, endostreym.com and lat.care share IP numbers with planogy.com.

planogy.com is delegated to four name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.

At least part of the name servers for planogy.com are shared with other domains, for instance signaling.info, sthonoreinv.com, imcharlie.co.uk, carolinedoughty.com and revenuedemand.com.

Host names with two IP numbers:

ns-cloud-b1.googledomains.com points to: 2001:4860:4802:32::6b and 216.239.32.107

ns-cloud-b2.googledomains.com points to: 2001:4860:4802:34::6b and 216.239.34.107

ns-cloud-b3.googledomains.com points to: 2001:4860:4802:36::6b and 216.239.36.107

ns-cloud-b4.googledomains.com points to: 2001:4860:4802:38::6b and 216.239.38.107

planogy.com 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.

planogy.com shares at least some mail servers with other domains, for example ns500731.ns500731.ns500731.ns500742.ns500704.ns500671.ns500705.ns500688.ns500671.ns500653.ns500153.tenderladiesbz.com, ns500758.ns500759.ns500698.ns500735.ns500736.ns500736.ns500708.ns500698.ns500708.ns500686.ns500652.ns500576.trackreceptor.com, ns500754.ns500754.ns500731.ns500704.ns500704.ns500704.ns500688.ns500704.ns500705.ns500666.ns500666.ns500291.ns500131.lustychickser.com, ns500671.ns500731.ns500742.ns500731.ns500671.ns500688.ns500704.ns500704.ns500678.ns500705.ns500671.ns500688.ns500649.ns500649.ns500666.ns500142.lustyslutz.com and ns500758.ns500758.ns500698.ns500758.ns500698.ns500698.ns500736.ns500735.ns500735.ns500708.ns500619.ns500652.ns500576.trackreceptor.com.

These mail servers are commonly used alongside aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx5.googlemail.com and aspmx4.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4004:c1d::1b and 142.251.167.26

alt1.aspmx.l.google.com points to 2a00:1450:400b:c02::1b and 172.253.116.27

alt2.aspmx.l.google.com points to 2a00:1450:4009:c0f::1b and 192.178.223.26