CF1762176352844-tsm20251102073205

NSLIST.NET - myregistry.us

Search for IP or hostnames:

myregistry.us checked at 2025-11-03T13:25:52.828Z 214ms 124/124/124 100% R:18

myregistry.us

NSns1-33.azure-dns.com
A2603:1061:0:10::21 ๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns1-33.azure-dns.com
A150.171.10.33๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns1-33.azure-dns.com
NSns4-33.azure-dns.info
A2620:1ec:bda:10::21 ๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns4-33.azure-dns.info
A13.107.206.33๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns4-33.azure-dns.info
NSns2-33.azure-dns.net
A2620:1ec:8ec:10::21 ๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns2-33.azure-dns.net
A150.171.16.33๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns2-33.azure-dns.net
NSns3-33.azure-dns.org
A2a01:111:4000:10::21 ๐Ÿ‡ฌ๐Ÿ‡ง Microsoft
PTRns3-33.azure-dns.org
A13.107.222.33๐Ÿ‡บ๐Ÿ‡ธ Microsoft
PTRns3-33.azure-dns.org
MXaspmx.l.google.com
A2607:f8b0:4004:c1d::1b ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRww-in-f27.1e100.net
A192.178.218.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyuiadtq-in-f27.1e100.net
MXalt1.aspmx.l.google.com
A2607:f8b0:4023:100f::1b ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwra-in-f27.1e100.net
A192.178.220.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwra-in-f27.1e100.net
MXalt2.aspmx.l.google.com
A2a00:1450:400c:c00::1b ๐Ÿ‡ง๐Ÿ‡ช Google
PTRws-in-f27.1e100.net
PTRws-in-x1b.1e100.net
A173.194.76.26๐Ÿ‡บ๐Ÿ‡ธ Google
PTRws-in-f26.1e100.net
MXalt3.aspmx.l.google.com
A2a00:1450:4025:402::1b ๐Ÿ‡ณ๐Ÿ‡ฑ Google
PTRrb-in-f27.1e100.net
A142.250.102.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRrb-in-f27.1e100.net
MXalt4.aspmx.l.google.com
A2a00:1450:4013:c1e::1a ๐Ÿ‡ณ๐Ÿ‡ฑ Google
PTRyugrqzs-in-f26.1e100.net
A192.178.213.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyugrqzs-in-f27.1e100.net

us

NSb.cctld.us
NSf.cctld.us
NSk.cctld.us
NSm.cctld.us
NSn.cctld.us
NSw.cctld.us
NSx.cctld.us
NSy.cctld.us

Starts with same word

Starts similarily

AI analysis

myregistry.us is delegated to four name servers: ns1-33.azure-dns.com, ns4-33.azure-dns.info, ns2-33.azure-dns.net and ns3-33.azure-dns.org.

myregistry.us shares name servers with other domains at least partially, for example allenandovary.com, mail.cargo.fo, siccobsolutions.com.mx, rrs.service.commerce.microsoft.com and ivia.me.

Host names with two IP numbers:

ns1-33.azure-dns.com points to: 2603:1061:0:10::21 and 150.171.10.33

ns4-33.azure-dns.info points to: 2620:1ec:bda:10::21 and 13.107.206.33

ns2-33.azure-dns.net points to: 2620:1ec:8ec:10::21 and 150.171.16.33

ns3-33.azure-dns.org points to: 2a01:111:4000:10::21 and 13.107.222.33

Five mail servers handle myregistry.us: 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.

myregistry.us shares mail servers with other domains at least partially; for instance brusten.net, fordtampico.mx, akamaifinanceacademy.com, cured.health and gospelorbit.com.

These mail servers are often used alongside aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2607:f8b0:4004:c1d::1b and 192.178.218.27

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

alt2.aspmx.l.google.com points to 2a00:1450:400c:c00::1b and 173.194.76.26

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

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

Perform reverse DNS lookup as well as normal forward DNS. Check Autonomous System Numbers (ASNs) and BGP connections between Internet Service Providers.
dbq

sMZDVVZ CF johedugfp 2025-11-03