`velazquez.us`

DNSSEC	⚠️ Not signed
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com`
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com`
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`velazquez-us.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01703.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c936::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f90a::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn6pr02cu00300.inbound.protection.outlook.com`
		A	52.101.8.34^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	52.101.40.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr05cu00100.inbound.protection.outlook.com`
		A	52.101.50.1^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr05cu00401.inbound.protection.outlook.com`
		A	52.101.194.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00605.inbound.protection.outlook.com`
TXT	`mscid=7FrA95YiYCssucuivrQmWPmV1BhnoxDIBeFfAVuzcEAIb+tc8AKFU14oLsId7tXIcTmo/Qv...`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=1

`us`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.cctld.us` ⭐
	NS	`b.cctld.us`
	NS	`f.cctld.us`
	NS	`k.cctld.us`
	NS	`m.cctld.us`
	NS	`n.cctld.us`
	NS	`w.cctld.us`
	NS	`x.cctld.us`
	NS	`y.cctld.us`
	SOA	`a.cctld.us`admin@tldns.godaddy serial=1785113770

Same first word

velazquez.net

velazquez.be

velazquez.us

velazquez.es

DNS History

9 records (5 active, 4 former)

●NSns1.bdm.microsoftonline.com2020-03-21 → 2026-07-27 · 3 obs

○ 2017-04-04 22:38:28
● 2020-03-21 16:30:12
● 2026-07-27 01:46:40

●NSns2.bdm.microsoftonline.com2020-03-21 → 2026-07-27 · 3 obs

○ 2017-04-04 22:38:28
● 2020-03-21 16:30:12
● 2026-07-27 01:46:40

●NSns3.bdm.microsoftonline.com2020-03-21 → 2026-07-27 · 3 obs

○ 2017-04-04 22:38:28
● 2020-03-21 16:30:12
● 2026-07-27 01:46:40

●NSns4.bdm.microsoftonline.com2020-03-21 → 2026-07-27 · 3 obs

○ 2017-04-04 22:38:28
● 2020-03-21 16:30:12
● 2026-07-27 01:46:40

○NSns49.worldnic.com2015-06-26 → 2017-04-04 · 4 obs

● 2015-06-26 13:19:20
● 2017-04-04 22:38:28
○ 2020-03-21 16:30:12
○ 2026-07-27 01:46:40

○NSns50.worldnic.com2015-06-26 → 2017-04-04 · 4 obs

● 2015-06-26 13:19:20
● 2017-04-04 22:38:28
○ 2020-03-21 16:30:12
○ 2026-07-27 01:46:40

○MXsmtp.velazquez.us2015-06-26 → 2017-04-04 · 4 obs

● 2015-06-26 13:19:20
● 2017-04-04 22:38:28
○ 2020-03-21 16:30:12
○ 2026-07-27 01:46:40

●MXvelazquez-us.mail.protection.outlook.com2020-03-21 → 2026-07-27 · 3 obs

○ 2017-04-04 22:38:28
● 2020-03-21 16:30:12
● 2026-07-27 01:46:40

○A205.178.189.1292015-06-26 → 2017-04-04 · 4 obs

● 2015-06-26 13:19:20
● 2017-04-04 22:38:28
○ 2020-03-21 16:30:12
○ 2026-07-27 01:46:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
us	b.cctld.us, f.cctld.us, k.cctld.us, m.cctld.us...	-
velazquez.us	ns2.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com	-

✅ Authoritative Response

Server:150.171.21.208

NS records: ns2.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for velazquez.us (unsigned zone)

⏱️ Timing

Total: 535ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`velazquez-us.mail.protection.outlook.com`
TXT	2	`mscid=7FrA95YiYCssucuivrQmWPmV1BhnoxDIBe, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

Analysis

Name Servers

Four name servers handle the delegation for velazquez.us: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

The name servers of velazquez.us overlap at least partially with those of other domains — among them traralgonrsl.com, hoyca.pt, vadikaratoprakli.com and two more.

Each of the four hosts ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com has two IP addresses. ns1.bdm.microsoftonline.com points to 13.107.236.208 and 2603:1061:0:700::d0. ns2.bdm.microsoftonline.com points to 150.171.21.208 and 2620:1ec:8ec:700::d0. ns3.bdm.microsoftonline.com points to 204.14.183.208 and 2a01:111:4000:700::d0. ns4.bdm.microsoftonline.com points to 208.84.5.208 and 2620:1ec:bda:700::d0.

Mail Servers

velazquez.us uses one mail server — velazquez-us.mail.protection.outlook.com.

velazquez-us.mail.protection.outlook.com has 8 IP addresses: 52.101.8.34, 52.101.40.24, 52.101.50.1 plus 5 more.

velazquez.us - robtex.com

velazquez.us

us

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Name Servers

Mail Servers

`velazquez.us`

`us`