DNSWHOIS.INFO - yhp.io

Search for IP or hostnames:

yhp.io checked at 2025-09-07T01:33:14.339Z 315ms 153/153/153 100% R:22

`yhp.io`

NS	`ns-125.awsdns-15.com`
		A	2600:9000:5300:7d00::1 ^{🇺🇸 Amazon}
			PTR	`ns-125.awsdns-15.com`
		A	205.251.192.125^{🇺🇸 Amazon}
			PTR	`ns-125.awsdns-15.com`
NS	`ns-631.awsdns-14.net`
		A	2600:9000:5302:7700::1 ^{🇺🇸 Amazon}
			PTR	`ns-631.awsdns-14.net`
		A	205.251.194.119^{🇺🇸 Amazon}
			PTR	`ns-631.awsdns-14.net`
NS	`ns-1409.awsdns-48.org`
		A	2600:9000:5305:8100::1 ^{🇺🇸 Amazon}
			PTR	`ns-1409.awsdns-48.org`
		A	205.251.197.129^{🇺🇸 Amazon}
			PTR	`ns-1409.awsdns-48.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1b::1b ^{🇺🇸 Google}
			PTR	`wv-in-f27.1e100.net`
		A	192.178.218.26^{🇺🇸 Google}
			PTR	`yuiadtq-in-f26.1e100.net`
NS	`ns-1610.awsdns-09.co.uk`
		A	2600:9000:5306:4a00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1610.awsdns-09.co.uk`
		A	205.251.198.74^{🇺🇸 Amazon}
			PTR	`ns-1610.awsdns-09.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google}
			PTR	`dj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1b ^{🇧🇪 Google}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.27^{🇺🇸 Google}
			PTR	`ws-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1a ^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1a ^{🇳🇱 Google}
			PTR	`yugrqog-in-f26.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	3.167.99.30^{🇺🇸 Amazon}
		PTR	`server-3-167-99-30.iad55.r.cloudfront.net`
A	3.167.99.47^{🇺🇸 Amazon}
		PTR	`server-3-167-99-47.iad55.r.cloudfront.net`
A	3.167.99.79^{🇺🇸 Amazon}
		PTR	`server-3-167-99-79.iad55.r.cloudfront.net`
A	3.167.99.83^{🇺🇸 Amazon}
		PTR	`server-3-167-99-83.iad55.r.cloudfront.net`

`io`

	NS	`a0.nic.io`
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`

Starts with same word
`yhp.org.uk`
`yhp.org`
`yhp.co`
`yhp.ir`
`yhp.eu`
`yhp.it`
`yhp.ru`
`yhp.co.nz`
`yhp.io`
`yhp.co.za`
`yhp.us`
`yhp.com`
`yhp.com.au`
`yhp.fr`
`yhp.be`
`yhp.dyndns.org`
`yhp.jp`

Starts similarily
`hyp.no`
`hpy.be`
`hyp.co.il`
`hpy.org`
`hyp.com.mx`
`hyp.is`
`hyp.la`
`yph.me`
`hpy.fi`
`yhp.org.uk`
`pyh.net`
`hyp.cn`
`phy.tw`
`hyp.pt`
`hyp.nl`
`pyh.ru`
`phy.ca`
`pyh.com`
`phy.nl`
`hpy.us`
`hpy.net`
`phy.se`
`hyp.cc`
`phy.ch`
`phy.com.tw`
`hyp.sakura.ne.jp`
`yhp.org`
`phy.com`
`hyp.gr`
`hyp.co.nz`
`hyp.edu.vn`
`hyp.be`
`hyp.pl`
`phy.be`
`pyh.ir`
`yhp.co`
`yhp.ir`
`hyp.me`
`hyp.co`
`yph.cn`
`hyp.life`
`yhp.eu`
`hyp.tv`
`yph.de`
`phy.im`
`hyp.com.au`
`hyp.guru`
`yhp.it`
`pyh.eu`
`yph.co`
`hpy.de`
`hpy.it`
`phy.cc`
`pyh.be`
`hyp.hu`
`yph.us`
`hyp.fr`
`pyh.co`
`phy.health`
`hyp.ru`
`phy.it`
`hyp.ee`
`phy.re`
`hpy.com.sg`
`hyp.at`
`hpy.at`
`hyp.org.tr`
`phy.hk`
`hyp.by`
`hyp.mobi`
`hpy.com`
`pyh.dk`
`phy.at`
`pyh.us`
`phy.si`
`yph.fi`
`hpy.bz`
`phy.is`
`yph.com`
`hpy.co`
`phy.hr`
`hyp.dk`
`hyp.fm`
`yph.it`
`pyh.ca`
`yph.org`
`yhp.ru`
`yph.cz`
`hpy.com.cn`
`yph.at`
`hyp.ac.uk`
`phy.dk`
`hyp.jp`
`yph.su`
`phy.media`
`pyh.cn`
`phy.ru`
`yhp.co.nz`
`phy.eu`
`yhp.io`
`phy.de`
`pyh.it`
`yhp.co.za`
`yhp.us`
`hyp.org`
`pyh.in`
`phy.digital`
`hyp.eu`
`hyp.ch`
`hyp.us`
`hyp.net`
`yph.nl`
`phy.com.br`
`yhp.com`
`hyp.se`
`hyp.net.au`
`yhp.com.au`
`yph.be`
`yph.ru`
`hyp.in`
`yhp.fr`
`phy.jp`
`pyh.nl`
`yhp.be`
`pyh.es`
`phy.la`
`hyp.directory`
`yhp.dyndns.org`
`phy.net`
`phy.io`
`hyp.biz`
`yhp.jp`
`hyp.fi`
`hpy.cz`
`yph.es`
`yph.in`
`yph.net`
`hpy.me`

AI analysis

The DNS record yhp.io resolves to the following IP addresses: 3.167.99.30, 3.167.99.47, 3.167.99.79, and 3.167.99.83.

IP numbers are shared between yhp.io and other host names like devyourself.com, s1178.photobucket.com, royalcanin.gr, s891.photobucket.com, and beloved.tool.cxp.staging-traveloka.com.

The four name servers delegated to yhp.io are ns-125.awsdns-15.com, ns-631.awsdns-14.net, ns-1409.awsdns-48.org, and ns-1610.awsdns-09.co.uk.

The domain yhp.io shares its name servers, at least partially, with other domains such as goodgrief.net, fullcast.io, etransport.lt, muhlenbergsoftballcamps.com, and ianguile.com.

The name servers ns-270.awsdns-33.com, ns-670.awsdns-19.net, ns-1588.awsdns-06.co.uk, ns-1844.awsdns-38.co.uk, ns-128.awsdns-16.com, ns-1296.awsdns-34.org, ns-748.awsdns-29.net, ns-1845.awsdns-38.co.uk, ns-794.awsdns-35.net, and ns-968.awsdns-57.net are typically used in conjunction.

ns-125.awsdns-15.com, ns-631.awsdns-14.net, ns-1409.awsdns-48.org, and ns-1610.awsdns-09.co.uk point to two IP numbers each: 2600:9000:5300:7d00::1 and 205.251.192.125, 2600:9000:5302:7700::1 and 205.251.194.119, 2600:9000:5305:8100::1 and 205.251.197.129, 2600:9000:5306:4a00::1 and 205.251.198.74 respectively.

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, are in charge of handling yhp.io.

Other domains such as ysterneng.com, lightandclarity.com, ginosonline.com, rufoa.com, and msert.net share some mail servers, at least partially, with yhp.io.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are typically utilized in conjunction.

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 each point to two IP numbers: 2607:f8b0:4004:c1b::1b and 192.178.218.26, 2a00:1450:400b:c02::1a and 172.253.116.26, 2a00:1450:400c:c00::1b and 173.194.76.27, 2a00:1450:4025:402::1a and 142.250.102.26, 2a00:1450:4013:c1c::1a and 192.178.156.26 respectively.

dbq