CF1763046622321-tsm20251109205412

DNSWHOIS.INFO - myregistry.us

Search for IP or hostnames:

myregistry.us checked at 2025-11-13T15:10:22.267Z 1162ms 124/124/124 100% R:11 allDone:true timedOut:false

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:4023:c06::1a ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRdz-in-f26.1e100.net
A142.250.101.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRdz-in-f27.1e100.net
MXalt1.aspmx.l.google.com
A2607:f8b0:4023:100f::1b ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwra-in-f27.1e100.net
A192.178.220.26๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwra-in-f26.1e100.net
MXalt2.aspmx.l.google.com
A2607:f8b0:4023:1015::1b ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwta-in-f27.1e100.net
A172.253.135.26๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyudfwta-in-f26.1e100.net
MXalt3.aspmx.l.google.com
A2607:f8b0:4023:3001::1a ๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyulnkec-in-f26.1e100.net
A172.217.74.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRyulnkec-in-f27.1e100.net
MXalt4.aspmx.l.google.com
A2404:6800:4003:c06::1a ๐Ÿ‡ธ๐Ÿ‡ฌ Google
PTRsm-in-f26.1e100.net
A142.250.4.27๐Ÿ‡บ๐Ÿ‡ธ Google
PTRsm-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 delegates 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 at least partially shares name servers with other domains, including 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.

myregistry.us 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.

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

these mail servers are often used with 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:4023:c06::1a and 142.250.101.27.

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

alt2.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1b and 172.253.135.26.

alt3.aspmx.l.google.com points to: 2607:f8b0:4023:3001::1a and 172.217.74.27.

alt4.aspmx.l.google.com points to: 2404:6800:4003:c06::1a and 142.250.4.27.

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