WWW.ROBTEX.COM - metadatasync.com

Search for IP or hostnames:

metadatasync.com checked at 2025-09-28T13:28:23.491Z 2428ms 190/190/190 100% R:16

`metadatasync.com`

NS	`ns1.hover.com`
		A	2604:4000:0:d:216:40:47:26^{🇨🇦 Tucows}
			PTR	`ns1.hover.com`
		A	216.40.47.26^{🇨🇦 Tucows}
			PTR	`ns1.hover.com`
NS	`ns2.hover.com`
		A	2604:4000:2800:d:64:99:148:13^{🇨🇦 TUCOWS-3}
			PTR	`ns2.hover.com`
		A	64.98.148.13^{🇨🇦 TUCOWS-3}
			PTR	`ns2.hover.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1a^{🇺🇸 Google}
			PTR	`bk-in-f26.1e100.net`
		A	142.250.31.26^{🇺🇸 Google}
			PTR	`bj-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google}
			PTR	`dj-in-f27.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:4025:402::1a^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.27^{🇺🇸 Google}
			PTR	`rb-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1e::1b^{🇳🇱 Google}
			PTR	`yugrqzs-in-f27.1e100.net`
		A	192.178.213.26^{🇺🇸 Google}
			PTR	`yugrqzs-in-f26.1e100.net`
A	52.34.73.250^{🇺🇸 Amazon}
		PTR	`ec2-52-34-73-250.us-west-2.compute.amazonaws.com`

metadatasync.com

metadatasync.com

metadatasync.com resolves to one IP number: 52.34.73.250.

Other host names for instance rudd.ws and ec2-52-34-73-250.us-west-2.compute.amazonaws.com share IP numbers with metadatasync.com.

metadatasync.com's delegation uses two name servers: ns1.hover.com and ns2.hover.com.

metadatasync.com uses the same name server setup as other domains, such as salinized.com, s-naito.com, amfront.com, medwardscabinetry.com and vipebgeek.com.

Host names with two IPs:

metadatasync.com shares at least some mail servers with other domains, for example bitflut.com, rext.it, techprostudio.com, sdtlimo.com and keysolarsolutions.com.

Host names with two IP numbers:

dbq