CF1757202554597-tsm20250906182357

WWW.RTSAK.COM - mighty.com

Search for IP or hostnames:

mighty.com checked at 2025-09-06T23:49:14.545Z 356ms 138/138/138 100% R:11

`mighty.com`

	NS	`ns-183.awsdns-22.com`
			A	2600:9000:5300:b700::1 ^{🇺🇸 Amazon}
				PTR	`ns-183.awsdns-22.com`
			A	205.251.192.183^{🇺🇸 Amazon}
				PTR	`ns-183.awsdns-22.com`
	NS	`ns-563.awsdns-06.net`
			A	2600:9000:5302:3300::1 ^{🇺🇸 Amazon}
				PTR	`ns-563.awsdns-06.net`
			A	205.251.194.51^{🇺🇸 Amazon}
				PTR	`ns-563.awsdns-06.net`
	NS	`ns-1105.awsdns-10.org`
			A	2600:9000:5304:5100::1 ^{🇺🇸 Amazon}
				PTR	`ns-1105.awsdns-10.org`
			A	205.251.196.81^{🇺🇸 Amazon}
				PTR	`ns-1105.awsdns-10.org`
	MX	`aspmx.l.google.com`
			A	2607:f8b0:4004:c07::1a ^{🇺🇸 Google}
				PTR	`bc-in-f26.1e100.net`
			A	192.178.155.27^{🇺🇸 Google}
				PTR	`yuiadrs-in-f27.1e100.net`
	NS	`ns-1772.awsdns-29.co.uk`
			A	2600:9000:5306:ec00::1 ^{🇺🇸 Amazon}
				PTR	`ns-1772.awsdns-29.co.uk`
			A	205.251.198.236^{🇺🇸 Amazon}
				PTR	`ns-1772.awsdns-29.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::1a ^{🇧🇪 Google}
				PTR	`ws-in-f26.1e100.net`
				PTR	`ws-in-x1a.1e100.net`
			A	173.194.76.27^{🇺🇸 Google}
				PTR	`ws-in-f27.1e100.net`
	MX	`alt3.aspmx.l.google.com`
			A	2a00:1450:4010:c0e::1a ^{🇫🇮 Google}
				PTR	`lu-in-f26.1e100.net`
				PTR	`lu-in-x1a.1e100.net`
			A	74.125.131.27^{🇺🇸 Google}
				PTR	`lu-in-f27.1e100.net`
	MX	`alt4.aspmx.l.google.com`
			A	2404:6800:4003:c06::1a ^{🇸🇬 Google}
				PTR	`sm-in-f26.1e100.net`
			A	142.250.4.27^{🇺🇸 Google}
				PTR	`sm-in-f27.1e100.net`
	A	198.202.211.1^{🇺🇸 Fastly}

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

rank #792991 globally
rank #413055 in the tld

Starts with same word
`mighty.house`
`mighty.pro`
`mighty.org`
`mighty.cb.it`
`mighty.shopping`
`mighty.tv`
`mighty.pl`
`mighty.ru`
`mighty.parts`
`mighty.company`
`mighty.network`
`mighty.synology.me`
`mighty.email`
`mighty.me`
`mighty.net`
`mighty.com.au`
`mighty.productions`
`mighty.asia`
`mighty.fi`
`mighty.solutions`
`mighty.se`
`mighty.no`
`mighty.at`
`mighty.biz`
`mighty.co`
`mighty.it`
`mighty.agency`
`mighty.us`
`mighty.ne.jp`
`mighty.design`
`mighty.jp`
`mighty.wang`
`mighty.cc`
`mighty.cz`
`mighty.co.za`
`mighty.co.th`
`mighty.com`
`mighty.bio`
`mighty.su`
`mighty.la`
`mighty.ng`
`mighty.mx`
`mighty.gift`
`mighty.in`
`mighty.co.jp`
`mighty.systems`
`mighty.red`
`mighty.international`
`mighty.ca`
`mighty.ch`

Starts similarily
`mighty.ca`
`mighty.ch`
`mighty.house`
`mighty.pro`
`mighty.org`
`mighty.cb.it`
`mighty.shopping`
`mighty.tv`
`hitgym.club`
`mighty.pl`
`mighty.ru`
`mighty.parts`
`mighty.company`
`mighty.network`
`mighty.synology.me`
`mighty.email`
`mighty.me`
`mighty.net`
`mighty.com.au`
`mityhg.com`
`mighty.productions`
`mighty.asia`
`mighty.fi`
`mighty.solutions`
`mighty.se`
`mighty.no`
`mighty.at`
`mighty.biz`
`mighty.co`
`mighty.it`
`mighty.agency`
`mighty.us`
`mghtyi.org`
`mighty.ne.jp`
`mighty.design`
`mighty.jp`
`mighty.wang`
`mighty.cc`
`mighty.cz`
`hitgym.ru`
`mighty.co.za`
`mighty.co.th`
`myghit.com`
`mighty.com`
`mighty.bio`
`mighty.su`
`mighty.la`
`gymhit.com`
`mighty.ng`
`mighty.mx`
`mighty.gift`
`mighty.in`
`hitgym.com`
`mighty.co.jp`
`mighty.systems`
`mighty.red`
`mighty.international`

AI analysis

198.202.211.1 is the IP number that mighty.com points to.

IP numbers are shared between mighty.com and other host names such as triniqua.com, mccoyoutdoorco.com, kellybroganmd.com, morsa.com.mx, and myplan.cloud.

Four name servers, ns-183.awsdns-22.com, ns-563.awsdns-06.net, ns-1105.awsdns-10.org and ns-1772.awsdns-29.co.uk, are delegated to mighty.com.

The name servers of mighty.com are at least partially shared with other domains such as nemsnaturalgas.com, covid19diabetes.com, framingham.zensource.site, goldwellcap.com, and mobivity.com.

The name servers ns-910.awsdns-49.net, ns-1346.awsdns-40.org, ns-1550.awsdns-01.co.uk, ns-569.awsdns-07.net, ns-1740.awsdns-25.co.uk, ns-227.awsdns-28.com, ns-1680.awsdns-18.co.uk, ns-916.awsdns-50.net, ns-990.awsdns-59.net, and ns-312.awsdns-39.com are commonly used in conjunction.

Two IP numbers, 2600:9000:5300:b700::1 and 205.251.192.183, are pointed to by ns-183.awsdns-22.com. Similarly, ns-563.awsdns-06.net directs to 2600:9000:5302:3300::1 and 205.251.194.51. Moreover, ns-1105.awsdns-10.org is associated with 2600:9000:5304:5100::1 and 205.251.196.81, and ns-1772.awsdns-29.co.uk points to 2600:9000:5306:ec00::1 and 205.251.198.236.

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

Domains such as londoncentralcommunications.com, forempv.ccoo.es, colemedical.com, ensign-media.com, and algaebiomass.org share some mail servers, at least partially, with mighty.com.

The mail servers aspmx2.googlemail.com and aspmx3.googlemail.com are frequently used in conjunction with these mail servers.

aspmx.l.google.com, 2607:f8b0:4004:c07::1a, and 192.178.155.27 are related.

alt1.aspmx.l.google.com, 2a00:1450:400b:c02::1a, and 172.253.116.26 are connected.

alt2.aspmx.l.google.com, 2a00:1450:400c:c00::1a, and 173.194.76.27 are associated.

alt3.aspmx.l.google.com, 2a00:1450:4010:c0e::1a, and 74.125.131.27 are linked.

alt4.aspmx.l.google.com, 2404:6800:4003:c06::1a, and 142.250.4.27 are correlated.

dbq

UHXbHVM CF johedugfp 2025-09-06