security-sc.com - dns.ninja

`security-sc.com`

DNSSEC	⚠️ Not signed
NS	`ns1-36.azure-dns.com` ⭐
		A	2603:1061:0:10::24^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
		A	150.171.10.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-36.azure-dns.com`
NS	`ns2-36.azure-dns.net`
		A	2620:1ec:8ec:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
		A	150.171.16.36^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-36.azure-dns.net`
NS	`ns3-36.azure-dns.org`
		A	2a01:111:4000:10::24^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-36.azure-dns.org`
		A	13.107.222.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-36.azure-dns.org`
NS	`ns4-36.azure-dns.info`
		A	2620:1ec:bda:10::24^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
		A	13.107.206.36^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-36.azure-dns.info`
MX	`securitysc-com02b.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc1a::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::2^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00302.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::3^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00203.inbound.protection.outlook.com`
		A	52.101.124.0^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	52.101.124.1^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	52.101.124.6^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00206.inbound.protection.outlook.com`
		A	52.101.157.40^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
MX	`ms67103924.msv1.invalid`^(32767)
TXT	`v=spf1 ip4:20.222.34.123 include:spf.baremetal.jp ~all`
SOA	`ns1-36.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=1781879675

Same first word

security-sc.com

Similar names

cs-security.com

cs-security.de

cs-security.com.qa

security-cs.com

circus-stey.ch

cs-security.pl

cs-security.net

cs-security.org

DNS History

9 records (6 active, 3 former)

●NSns1-36.azure-dns.com2026-04-23 → 2026-06-19 · 3 obs

○ 2018-07-01 14:23:10
● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

●NSns2-36.azure-dns.net2026-04-23 → 2026-06-19 · 3 obs

○ 2018-07-01 14:23:10
● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

○NSns2.wixdns.net2018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:23:10
○ 2026-04-23 23:24:04
○ 2026-06-19 14:40:20

●NSns3-36.azure-dns.org2026-04-23 → 2026-06-19 · 3 obs

○ 2018-07-01 14:23:10
● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

○NSns3.wixdns.net2018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:23:10
○ 2026-04-23 23:24:04
○ 2026-06-19 14:40:20

●NSns4-36.azure-dns.info2026-04-23 → 2026-06-19 · 3 obs

○ 2018-07-01 14:23:10
● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

●MXms67103924.msv1.invalid2026-04-23 → 2026-06-19 · 2 obs

● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

●MXsecuritysc-com02b.mail.protection.outlook.com2026-04-23 → 2026-06-19 · 2 obs

● 2026-04-23 23:24:04
● 2026-06-19 14:40:20

○A23.236.62.1472018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:23:10
○ 2026-04-23 23:24:04
○ 2026-06-19 14:40:20

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:150.171.16.36

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for security-sc.com (unsigned zone)

⏱️ Timing

Total: 278ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-36.azure-dns.com, ns2-36.azure-dns.net...`
MX	2	`ms67103924.msv1.invalid (pri: 32767), securitysc-com02b.mail.protection.outloo`
TXT	1	`v=spf1 ip4:20.222.34.123 include:spf.bar`
SOA	1	`ns1-36.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

Four name servers handle the delegation for security-sc.com: ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org.

The name servers of security-sc.com overlap at least partially with those of other domains — among them hyperlan.com.br, unimedjaboticabal.coop.br, images.hawaiianairlines.com and two more.

Each of the four hosts ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org has two IP addresses. ns1-36.azure-dns.com points to 150.171.10.36 and 2603:1061:0:10::24. ns4-36.azure-dns.info points to 13.107.206.36 and 2620:1ec:bda:10::24. ns2-36.azure-dns.net points to 150.171.16.36 and 2620:1ec:8ec:10::24. ns3-36.azure-dns.org points to 13.107.222.36 and 2a01:111:4000:10::24.

Mail Servers

security-sc.com uses two mail servers, ms67103924.msv1.invalid and securitysc-com02b.mail.protection.outlook.com.

Hosts with 8 IP addresses each:

securitysc-com02b.mail.protection.outlook.com resolves to 52.101.124.0, 52.101.124.1, 52.101.124.6 and 5 other IP addresses.