`lockreporting.com`

DNSSEC	⚠️ Not signed
A	9.169.142.232^{🇺🇸 Microsoft9.169.0.0/16}
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1774526022

Same first word

lockreporting.com

DNS History

8 records (5 active, 3 former)

●NSns1-02.azure-dns.com2026-03-21 → 2026-03-26 · 3 obs

○ 2020-04-09 02:02:24
● 2026-03-21 17:18:24
● 2026-03-26 12:11:50

●NSns2-02.azure-dns.net2026-03-21 → 2026-03-26 · 3 obs

○ 2020-04-09 02:02:24
● 2026-03-21 17:18:24
● 2026-03-26 12:11:50

●NSns3-02.azure-dns.org2026-03-21 → 2026-03-26 · 3 obs

○ 2020-04-09 02:02:24
● 2026-03-21 17:18:24
● 2026-03-26 12:11:50

○NSns39.domaincontrol.com2020-04-09 → 2020-04-09 · 3 obs

● 2020-04-09 02:02:24
○ 2026-03-21 17:18:24
○ 2026-03-26 12:11:50

●NSns4-02.azure-dns.info2026-03-21 → 2026-03-26 · 3 obs

○ 2020-04-09 02:02:24
● 2026-03-21 17:18:24
● 2026-03-26 12:11:50

○NSns40.domaincontrol.com2020-04-09 → 2020-04-09 · 3 obs

● 2020-04-09 02:02:24
○ 2026-03-21 17:18:24
○ 2026-03-26 12:11:50

○A200.60.68.702020-04-09 → 2020-04-09 · 3 obs

● 2020-04-09 02:02:24
○ 2026-03-21 17:18:24
○ 2026-03-26 12:11:50

●A9.169.142.2322026-03-21 → 2026-03-26 · 3 obs

○ 2020-04-09 02:02:24
● 2026-03-21 17:18:24
● 2026-03-26 12:11:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
lockreporting.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.2

NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for lockreporting.com (unsigned zone)

⏱️ Timing

Total: 214ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`9.169.142.232`
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
SOA	1	`ns1-02.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

IP Addresses

lockreporting.com resolves to one IP number: 9.169.142.232.

Name Servers

lockreporting.com 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.

lockreporting.com at least partially shares name servers with other domains, for instance uponor.kr, oem-info.com, ckipe.net, arudhasif.com and just-eat.co.il.

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.

lockreporting.com - robtex.com