DNSWHOIS.INFO - solapi.com

Search for IP or hostnames:

solapi.com checked at 2025-09-06T09:56:05.176Z 5545ms 148/148/148 100% R:13

`solapi.com`

NS	`ns-461.awsdns-57.com`
		A	2600:9000:5301:cd00::1 ^{🇺🇸 Amazon}
			PTR	`ns-461.awsdns-57.com`
		A	205.251.193.205^{🇺🇸 Amazon}
			PTR	`ns-461.awsdns-57.com`
NS	`ns-766.awsdns-31.net`
		A	2600:9000:5302:fe00::1 ^{🇺🇸 Amazon}
			PTR	`ns-766.awsdns-31.net`
		A	205.251.194.254^{🇺🇸 Amazon}
			PTR	`ns-766.awsdns-31.net`
NS	`ns-1156.awsdns-16.org`
		A	2600:9000:5304:8400::1 ^{🇺🇸 Amazon}
			PTR	`ns-1156.awsdns-16.org`
		A	205.251.196.132^{🇺🇸 Amazon}
			PTR	`ns-1156.awsdns-16.org`
MX	`aspmx.l.google.com`
		A	2a00:1450:400c:c09::1b ^{🇧🇪 Google}
			PTR	`wm-in-f27.1e100.net`
			PTR	`wm-in-x1b.1e100.net`
		A	142.251.173.26^{🇺🇸 Google}
			PTR	`wi-in-f26.1e100.net`
NS	`ns-1798.awsdns-32.co.uk`
		A	2600:9000:5307:600::1 ^{🇺🇸 Amazon}
			PTR	`ns-1798.awsdns-32.co.uk`
		A	205.251.199.6^{🇺🇸 Amazon}
			PTR	`ns-1798.awsdns-32.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:4025:c01::1b ^{🇵🇱 Google}
			PTR	`rd-in-f27.1e100.net`
		A	142.250.147.26^{🇺🇸 Google}
			PTR	`rd-in-f26.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::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	3.34.235.12^{🇰🇷 Amazon}
		PTR	`ec2-3-34-235-12.ap-northeast-2.compute.amazonaws.com`
A	13.124.153.246^{🇰🇷 Amazon}
		PTR	`ec2-13-124-153-246.ap-northeast-2.compute.amazonaws.com`
A	13.209.108.31^{🇰🇷 Amazon}
		PTR	`ec2-13-209-108-31.ap-northeast-2.compute.amazonaws.com`

`com`

	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`

Starts with same word
`solapi.net`
`solapi.com`

Starts similarily
`posila.com`
`sipola.org`
`siapol.es`
`lopais.com`
`aspoli.com`
`saipol.pl`
`apolis.cz`
`plasio.gr`
`polisa.news`
`polisa.com`
`paliso.de`
`pisola.com`
`aspoli.ro`
`sopila.com`
`alipso.com.ar`
`alipso.com`
`oilspa.pl`
`sipola.fi`
`pilosa.org`
`oilspa.win`
`spiola.net`
`apolis.at`
`apolis.org`
`opalis.nl`
`apolis.eu`
`polisa.de`
`apolis.co`
`aposil.com`
`piolas.com`
`polisa.it`
`ipasol.co.uk`
`saipol.com`
`solipa.com`
`apolis.gr`
`saipol.com.au`
`apolis.si`
`apolis.de`
`ipasol.net`
`opalis.be`
`sipola.se`
`apisol.es`
`alpsio.com`
`opalis.com`
`spolia.de`
`spiola.at`
`paliso.com`
`isopal.de`
`apisol.de`
`alpiso.com`
`spliao.info`
`polais.com`
`palosi.com`
`ipasol.eu`
`soalpi.com`
`apolis.in`
`liposa.com`
`oplisa.com`
`solapi.net`
`polisa.pl`
`alopis.com`
`apolis.ru`
`palios.de`
`pilosa.com`
`pilosa.de`
`loapsi.com`
`posila.cz`
`alipos.id`
`opsial.eu`
`spiola.com`
`isopla.com`
`aliops.com`
`opalis.org`
`polisa.co`
`apisol.com`
`apilos.com`
`spaoil.cn`
`apolis.biz`
`oailsp.ca`
`piosla.pl`
`ipasol.com`
`sipola.net`
`ipasol.de`
`spliao.cn`
`siapol.it`
`pasoil.cz`
`paliso.ca`
`solipa.fr`
`apilos.jp`
`oilspa.ru`
`polisa.eu`
`apolis.myshopify.com`
`oilspa.com`
`oilasp.com`
`apoils.com`
`palios.com`
`sipalo.com`
`aspoli.ua`
`saipol.fr`
`apolis.it`
`polisa.com.pe`
`ilopsa.com`
`alipos.com`
`opilas.com`
`solapi.com`
`apolis.com.pl`
`psiola.ru`
`spolia.it`
`pasoil.com`
`opalis.ru`
`opsail.org`
`opalis.de`
`alpiso.net`
`alpiso.es`
`asipol.org`
`apolis.es`
`poiasl.com`
`pisalo.net`

AI analysis

solapi.com is configured to point to three IP addresses: 3.34.235.12, 13.124.153.246, and 13.209.108.31.

The IP numbers of solapi.com are shared with other host names such as ec2-13-124-153-246.ap-northeast-2.compute.amazonaws.com, ec2-3-34-235-12.ap-northeast-2.compute.amazonaws.com, and ec2-13-209-108-31.ap-northeast-2.compute.amazonaws.com.

Four name servers, ns-461.awsdns-57.com, ns-766.awsdns-31.net, ns-1156.awsdns-16.org and ns-1798.awsdns-32.co.uk, are delegated to solapi.com.

The name servers of solapi.com are at least partially shared with other domains such as emailconnexion.com, d2c87067d3d9q7.cloudfront.net, teradigitalluggage.com, haien-yobou.jp, and iblacklist.net.

The name servers ns-336.awsdns-42.com, ns-1154.awsdns-16.org, ns-1701.awsdns-20.co.uk, ns-1552.awsdns-02.co.uk, ns-170.awsdns-21.com, ns-991.awsdns-59.net, and ns-1762.awsdns-28.co.uk are frequently utilized in conjunction.

Two IP numbers, 2600:9000:5301:cd00::1 and 205.251.193.205, are pointed to by ns-461.awsdns-57.com. Similarly, ns-766.awsdns-31.net directs to 2600:9000:5302:fe00::1 and 205.251.194.254. Moreover, ns-1156.awsdns-16.org is associated with 2600:9000:5304:8400::1 and 205.251.196.132, and ns-1798.awsdns-32.co.uk points to 2600:9000:5307:600::1 and 205.251.199.6.

The 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 responsible for handling solapi.com.

Domains such as quotera.com, silverlinecrm.com, ido3d.com, phatdiem.org, and flowsoft.com.mx share some mail servers, at least partially, with solapi.com.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, and inbound-smtp.eu-west-1.amazonaws.com are commonly 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: 2a00:1450:400c:c09::1b and 142.251.173.26, 2a00:1450:4013:c1c::1b and 192.178.156.26, 2a00:1450:4025:c01::1b and 142.250.147.26, 2a00:1450:4025:402::1a and 142.250.102.26, 2a00:1450:4013:c1c::1b and 192.178.156.27 respectively.

dbq