WWW.ROBTEX.COM - picosecond.org

Search for IP or hostnames:

picosecond.org checked at 2025-09-05T18:59:41.573Z 107ms 211/211/211 100% R:13

`picosecond.org`

NS	`ns-cloud-d1.googledomains.com`
		A	2001:4860:4802:32::6d^{🇺🇸 Google}
			PTR	`ns-cloud-d1.googledomains.com`
		A	216.239.32.109^{🇺🇸 Google}
			PTR	`ns-cloud-d1.googledomains.com`
NS	`ns-cloud-d2.googledomains.com`
		A	2001:4860:4802:34::6d^{🇺🇸 Google}
			PTR	`ns-cloud-d2.googledomains.com`
		A	216.239.34.109^{🇺🇸 Google}
			PTR	`ns-cloud-d2.googledomains.com`
NS	`ns-cloud-d3.googledomains.com`
		A	2001:4860:4802:36::6d^{🇺🇸 Google}
			PTR	`ns-cloud-d3.googledomains.com`
		A	216.239.36.109^{🇺🇸 Google}
			PTR	`ns-cloud-d3.googledomains.com`
NS	`ns-cloud-d4.googledomains.com`
		A	2001:4860:4802:38::6d^{🇺🇸 Google}
			PTR	`ns-cloud-d4.googledomains.com`
		A	216.239.38.109^{🇺🇸 Google}
			PTR	`ns-cloud-d4.googledomains.com`
MX	`in1-smtp.messagingengine.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`in2-smtp.messagingengine.com`
		A	202.12.124.216^AS5716
			PTR	`stl-mx-01.messagingengine.com`
		A	202.12.124.217^AS5716
			PTR	`stl-mx-02.messagingengine.com`

`org`

	NS	`a0.org.afilias-nst.info`
	NS	`a2.org.afilias-nst.info`
	NS	`c0.org.afilias-nst.info`
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`d0.org.afilias-nst.org`

Up
`mirror.picosecond.org`
`ns2.picosecond.org`
`margaret.picosecond.org`
`mx0.picosecond.org`
`ruthenium.picosecond.org`
`figaro.picosecond.org`
`ns0.picosecond.org`
`ns1.picosecond.org`
`mx1.picosecond.org`
`litharge.picosecond.org`
`myla.picosecond.org`

Starts with same word
`picosecond.cn`
`picosecond.org`

Starts similarily
`endoscopic.jp`
`spicecondo.com`
`picosecond.cn`
`epiccondos.com`
`picosecond.org`

AI analysis

Host names mirror.picosecond.org, ns2.picosecond.org, margaret.picosecond.org, mx0.picosecond.org, ruthenium.picosecond.org and a few others, all have picosecond.org as their parent.

The four name servers to which picosecond.org is delegated are ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, and ns-cloud-d4.googledomains.com.

Other domains, such as lexpay.net, casadecookies.com, dominosol.com, igest.cl, and tww-wholesale.com, share at least a part of their name servers with picosecond.org.

ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, and ns-cloud-d4.googledomains.com all point to two IP numbers each: 2001:4860:4802:32::6d and 216.239.32.109, 2001:4860:4802:34::6d and 216.239.34.109, 2001:4860:4802:36::6d and 216.239.36.109, 2001:4860:4802:38::6d and 216.239.38.109 respectively.

Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage picosecond.org.

Just like domains itconvey.com, lorentey.com, laken.net, trappe.eu, and int19h.org, picosecond.org also has the same mail server setup.

Some mail servers are at least partially shared between picosecond.org and other domains, such as zfgrpyyu.com.

in1-smtp.messagingengine.com is configured to point to eight IP numbers: 103.168.172.216, 103.168.172.217, 103.168.172.218, 103.168.172.219, 103.168.172.220, 103.168.172.221, 103.168.172.222, and 103.168.172.223.

Similarly, in2-smtp.messagingengine.com is set to point to two IP numbers: 202.12.124.216 and 202.12.124.217.

dbq