NSLIST.NET - myserve.co

Search for IP or hostnames:

myserve.co checked at 2025-10-30T20:14:34.733Z 1488ms 124/124/124 100% R:11

`myserve.co`

NS	`ns-378.awsdns-47.com`
		A	2600:9000:5301:7a00::1 ^{🇺🇸 Amazon}
			PTR	`ns-378.awsdns-47.com`
		A	205.251.193.122^{🇺🇸 Amazon}
			PTR	`ns-378.awsdns-47.com`
NS	`ns-939.awsdns-53.net`
		A	2600:9000:5303:ab00::1 ^{🇺🇸 Amazon}
			PTR	`ns-939.awsdns-53.net`
		A	205.251.195.171^{🇺🇸 Amazon}
			PTR	`ns-939.awsdns-53.net`
NS	`ns-1475.awsdns-56.org`
		A	2600:9000:5305:c300::1 ^{🇺🇸 Amazon}
			PTR	`ns-1475.awsdns-56.org`
		A	205.251.197.195^{🇺🇸 Amazon}
			PTR	`ns-1475.awsdns-56.org`
NS	`ns-1697.awsdns-20.co.uk`
		A	2600:9000:5306:a100::1 ^{🇺🇸 Amazon}
			PTR	`ns-1697.awsdns-20.co.uk`
		A	205.251.198.161^{🇺🇸 Amazon}
			PTR	`ns-1697.awsdns-20.co.uk`
MX	`myserve-co.mail.protection.outlook.com`
		A	2a01:111:f403:c942:: ^{🇨🇦 Microsoft}
			PTR	`mail-yt5pr01cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c942::1 ^{🇨🇦 Microsoft}
			PTR	`mail-yt3pr01cu00701.inbound.protection.outlook.com`
		A	2a01:111:f403:c944:: ^{🇨🇦 Microsoft}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::1 ^{🇨🇦 Microsoft}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
		A	52.101.190.0^{🇨🇦 Microsoft}
			PTR	`mail-yt5pr01cu00100.inbound.protection.outlook.com`
		A	52.101.190.1^{🇨🇦 Microsoft}
			PTR	`mail-yt3pr01cu00701.inbound.protection.outlook.com`
		A	52.101.190.2^{🇨🇦 Microsoft}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	52.101.192.0^{🇨🇦 Microsoft}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
A	15.157.6.166^{🇨🇦 Amazon}
		PTR	`ec2-15-157-6-166.ca-central-1.compute.amazonaws.com`
A	15.223.93.107^{🇨🇦 Amazon}
		PTR	`ec2-15-223-93-107.ca-central-1.compute.amazonaws.com`

`co`

	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`

Up

dfi.myserve.co

www.myserve.co

Starts with same word

myserve.ch

myserve.co

myserve.de

myserve.ca

myserve.co.uk

myserve.net

myserve.app

myserve.com

Starts similarily

myserve.de

vmeyers.net

myverse.me

seemyrv.com

myverse.org

myserve.ca

meservy.org

servemy.us

myserve.co.uk

vermeys.com.au

myserve.net

svmeyer.com

myserve.app

servemy.biz

myserve.com

mysever.com

vermeys.com

mysever.net

myverse.site

servemy.org

myserve.ch

servemy.net

myersev.com

myverse.us

myverse.net

ymserve.com

svmeyer.de

myverse.com

myserve.co

AI analysis

myserve.co is the parent of dfi.myserve.co and www.myserve.co.

Two IP numbers are pointed to by myserve.co: 15.157.6.166 and 15.223.93.107.

other host names include ec2-15-157-6-166.ca-central-1.compute.amazonaws.com, dfi.myserve.co, smplx.co, www.myserve.co and ec2-15-223-93-107.ca-central-1.compute.amazonaws.com; they share IP numbers with myserve.co.

myserve.co delegates to four name servers: ns-378.awsdns-47.com, ns-939.awsdns-53.net, ns-1475.awsdns-56.org and ns-1697.awsdns-20.co.uk.

myserve.co at least partially shares name servers with other domains, for instance datenklar.de, limesurf.com, fatezerousa.com, facepay-jihanki.com and forge.tylertech.com.

These name servers are commonly used with ns-100.awsdns-12.com, ns-1444.awsdns-52.org, ns-708.awsdns-24.net, ns-965.awsdns-56.net and ns-642.awsdns-16.net.

Host names with two IP numbers: ns-378.awsdns-47.com points to 2600:9000:5301:7a00::1 and 205.251.193.122; ns-939.awsdns-53.net points to 2600:9000:5303:ab00::1 and 205.251.195.171; ns-1475.awsdns-56.org points to 2600:9000:5305:c300::1 and 205.251.197.195; ns-1697.awsdns-20.co.uk points to 2600:9000:5306:a100::1 and 205.251.198.161.

myserve.co is handled by a single mail server, myserve-co.mail.protection.outlook.com.

Hostname myserve-co.mail.protection.outlook.com resolves to eight IP numbers: 2a01:111:f403:c942::, 2a01:111:f403:c942::1, 2a01:111:f403:c944::, 2a01:111:f403:c944::1, 52.101.190.0, 52.101.190.1, 52.101.190.2 and 52.101.192.0.

dbq