DNSWHOIS.INFO - cloudflare-resolve-to.hostseo.com

Search for IP or hostnames:

cloudflare-resolve-to.hostseo.com checked at 2025-09-09T14:30:14.113Z 515ms 123/123/123 100% R:21

`cloudflare-resolve-to.hostseo.com`

CNAME	`hostseo.com`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1a ^{🇺🇸 Google}
			PTR	`bk-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
NS	`route-a1.cyberguard.seodns.one`
		A	185.136.96.77^{🇺🇸 ClouDNS}
			PTR	`dns1.cloudns.net`
NS	`route-a2.cyberguard.seodns.one`
		A	185.136.97.77^ClouDNS
			PTR	`dns2.cloudns.net`
NS	`route-a3.cyberguard.seodns.one`
		A	185.136.98.77^{🇺🇸 ClouDNS}
			PTR	`dns5.cloudns.net`
NS	`route-a4.cyberguard.seodns.one`
		A	185.136.99.77^ClouDNS
			PTR	`dns6.cloudns.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google}
			PTR	`dj-in-f27.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.26^{🇺🇸 Google}
			PTR	`ws-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::1a ^{🇳🇱 Google}
			PTR	`yugrqog-in-f26.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	37.114.48.5^{🇩🇪 SYNLINQ}
		PTR	`viper.server.gb.net`

`hostseo.com`

	MX	`aspmx.l.google.com`
	NS	`route-a1.cyberguard.seodns.one`
	NS	`route-a2.cyberguard.seodns.one`
	NS	`route-a3.cyberguard.seodns.one`
	NS	`route-a4.cyberguard.seodns.one`
	MX	`alt1.aspmx.l.google.com`
	MX	`alt2.aspmx.l.google.com`
	MX	`alt3.aspmx.l.google.com`
	MX	`alt4.aspmx.l.google.com`
	A	37.114.48.5^{🇩🇪 SYNLINQ}

AI analysis

37.114.48.5 is the IP number that cloudflare-resolve-to.hostseo.com points to.

IP numbers are shared between cloudflare-resolve-to.hostseo.com and other host names such as zelt.ae, viper.server.gb.net, hostseo.com, centriohost.com, and server.gb.net.

Four name servers, route-a1.cyberguard.seodns.one, route-a2.cyberguard.seodns.one, route-a3.cyberguard.seodns.one and route-a4.cyberguard.seodns.one, are delegated to cloudflare-resolve-to.hostseo.com.

The name servers of cloudflare-resolve-to.hostseo.com at least partially coincide with those of other domains, such as havehost.com and hostseo.com.

route-a1.cyberguard.seodns.one, route-a2.cyberguard.seodns.one, route-a3.cyberguard.seodns.one, and route-a4.cyberguard.seodns.one all point to respective IP numbers: 185.136.96.77, 185.136.97.77, 185.136.98.77, and 185.136.99.77.

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 cloudflare-resolve-to.hostseo.com.

Domains such as labofnac.com, oecgroup.net, ecu.lu, debraarchibald.com, and jasonajohnsonpsyd.com share some mail servers, at least partially, with cloudflare-resolve-to.hostseo.com.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, aspmx5.googlemail.com, and mx-capricab.easydns.com are typically used in conjunction.

aspmx.l.google.com, 2607:f8b0:4004:c19::1a, and 64.233.180.26 are related.

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

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

alt3.aspmx.l.google.com, 2a00:1450:4025:402::1a, and 142.250.102.26 are linked.

alt4.aspmx.l.google.com, 2a00:1450:4013:c1c::1a, and 192.178.156.27 are correlated.

dbq