NSLIST.NET - tryembrace.io

Search for IP or hostnames:

tryembrace.io checked at 2025-09-30T17:15:51.156Z 258ms 140/140/140 100% R:16

`tryembrace.io`

NS	`ns-289.awsdns-36.com`
		A	2600:9000:5301:2100::1 ^{🇺🇸 Amazon}
			PTR	`ns-289.awsdns-36.com`
		A	205.251.193.33^{🇺🇸 Amazon}
			PTR	`ns-289.awsdns-36.com`
NS	`ns-873.awsdns-45.net`
		A	2600:9000:5303:6900::1 ^{🇺🇸 Amazon}
			PTR	`ns-873.awsdns-45.net`
		A	205.251.195.105^{🇺🇸 Amazon}
			PTR	`ns-873.awsdns-45.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`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4023:c03::1b ^{🇺🇸 Google}
			PTR	`dy-in-f27.1e100.net`
		A	142.250.141.27^{🇺🇸 Google}
			PTR	`dd-in-f27.1e100.net`
NS	`ns-1574.awsdns-04.co.uk`
		A	2600:9000:5306:2600::1 ^{🇺🇸 Amazon}
			PTR	`ns-1574.awsdns-04.co.uk`
		A	205.251.198.38^{🇺🇸 Amazon}
			PTR	`ns-1574.awsdns-04.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2607:f8b0:4023:100f::1a ^{🇺🇸 Google}
			PTR	`yudfwra-in-f26.1e100.net`
		A	192.178.220.26^{🇺🇸 Google}
			PTR	`yudfwra-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2607:f8b0:4003:c30::1a ^{🇺🇸 Google}
			PTR	`yutulis-in-f26.1e100.net`
		A	74.125.27.26^{🇺🇸 Google}
			PTR	`yutulis-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.27^{🇺🇸 Google}
			PTR	`rb-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1e::1a ^{🇳🇱 Google}
			PTR	`yugrqzs-in-f26.1e100.net`
		A	192.178.213.27^{🇺🇸 Google}
			PTR	`yugrqzs-in-f27.1e100.net`
A	44.225.221.79^{🇺🇸 Amazon}
		PTR	`ec2-44-225-221-79.us-west-2.compute.amazonaws.com`
A	44.241.199.136^{🇺🇸 Amazon}
		PTR	`ec2-44-241-199-136.us-west-2.compute.amazonaws.com`

`io`

	NS	`a0.nic.io`
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`

Starts with same word

tryembrace.io

Starts similarily

tryembrace.io

cyberemart.co.kr

traceembry.org

AI analysis

tryembrace.io points to two IP numbers: 44.225.221.79 and 44.241.199.136.

tryembrace.io is delegated to four name servers: ns-289.awsdns-36.com, ns-873.awsdns-45.net, ns-1475.awsdns-56.org and ns-1574.awsdns-04.co.uk.

tryembrace.io at least partially shares name servers with other domains, for instance botibot.es, coupang.net, kintone-dev.com, music.com and blueapron.cooking.

These name servers are commonly used with ns-1322.awsdns-37.org, ns-1021.awsdns-63.net, ns-1184.awsdns-20.org, ns-1941.awsdns-50.co.uk, ns-1105.awsdns-10.org and ns-1239.awsdns-26.org.

Host names with two IP numbers:

ns-289.awsdns-36.com points to: 2600:9000:5301:2100::1 and 205.251.193.33.

ns-873.awsdns-45.net points to: 2600:9000:5303:6900::1 and 205.251.195.105.

ns-1475.awsdns-56.org points to: 2600:9000:5305:c300::1 and 205.251.197.195.

ns-1574.awsdns-04.co.uk points to: 2600:9000:5306:2600::1 and 205.251.198.38.

tryembrace.io is handled by 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.

tryembrace.io shares mail servers with other domains at least in part, for instance lewblackburn.com, ravenpack.com, asm.edu, burkecare.com and mdi.vc.

these mail servers are often used with aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4023:c03::1b and 142.250.141.27.

alt1.aspmx.l.google.com points to 2607:f8b0:4023:100f::1a and 192.178.220.26.

alt2.aspmx.l.google.com points to 2607:f8b0:4003:c30::1a and 74.125.27.26.

alt3.aspmx.l.google.com points to 2a00:1450:4025:402::1a and 142.250.102.27.

alt4.aspmx.l.google.com points to 2a00:1450:4013:c1e::1a and 192.178.213.27.

dbq