CF1760732787811-tsm20251017082432

MXLIST.NET - identity.events

Search for IP or hostnames:

identity.events checked at 2025-10-17T20:26:27.784Z 128ms 61/61/61 100% R:10

identity.events

NSns1-02.azure-dns.com
A2603:1061:0:700::2 🇺🇸 Microsoft
PTRns1-02.azure-dns.com
A13.107.236.2🇺🇸 Microsoft
PTRns1-02.azure-dns.com
NSns4-02.azure-dns.info
A2620:1ec:bda:700::2 🇺🇸 Microsoft
PTRns4-02.azure-dns.info
A208.84.5.2🇺🇸 Microsoft
PTRns4-02.azure-dns.info
NSns2-02.azure-dns.net
A2620:1ec:8ec:700::2 🇺🇸 Microsoft
PTRns2-02.azure-dns.net
A150.171.21.2🇺🇸 Microsoft
PTRns2-02.azure-dns.net
NSns3-02.azure-dns.org
A2a01:111:4000:700::2 🇬🇧 Microsoft
PTRns3-02.azure-dns.org
A204.14.183.2🇺🇸 Microsoft
PTRns3-02.azure-dns.org

events

NSv0n0.nic.events
NSv0n1.nic.events
NSv0n2.nic.events
NSv0n3.nic.events
NSv2n0.nic.events
NSv2n1.nic.events

Starts with same word

Starts similarily

AI analysis

identity.events is delegated to four name servers: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

identity.events at least partially shares name servers with other domains, for instance apconnected.com, 84.92.20.in-addr.arpa, nviso.de, glasgowmela.com and blu0.hotmail.com.

Host names with two IP numbers:

ns1-02.azure-dns.com points to 2603:1061:0:700::2 and 13.107.236.2; ns4-02.azure-dns.info points to 2620:1ec:bda:700::2 and 208.84.5.2; ns2-02.azure-dns.net points to 2620:1ec:8ec:700::2 and 150.171.21.2; ns3-02.azure-dns.org points to 2a01:111:4000:700::2 and 204.14.183.2.

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

XRuUpgz CF johedugfp 2025-10-17