CF1757145268632-tsm20250906072047

DNSWHOIS.INFO - identity.events

Search for IP or hostnames:

identity.events checked at 2025-09-06T07:54:28.610Z 229ms 61/61/61 100% R:8

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

AI analysis

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

For instance, the name servers of identity.events at least partially share with other domains such as apconnected.com, 84.92.20.in-addr.arpa, nviso.de, glasgowmela.com, and blu0.hotmail.com.

ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net, and ns3-02.azure-dns.org are DNS records that each point to two IP numbers: 2603:1061:0:700::2 and 13.107.236.2, 2620:1ec:bda:700::2 and 208.84.5.2, 2620:1ec:8ec:700::2 and 150.171.21.2, 2a01:111:4000:700::2 and 204.14.183.2 respectively.

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

vTLNesO CF johedugfp 2025-09-06