`yalesecurity.com`

DNSSEC	⚠️ Not signed
A	12.231.185.54^{🇺🇸 AS701812.128.0.0/9 12/8 upper half}
NS	`dns1.cscdns.net` ⭐
		A	2610:a1:1022::100^{🇺🇸 MAINT-ID-120082610:a1:1022::/48 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
		A	156.154.130.100^{🇺🇸 MAINT-ID-12008156.154.130.0/24 Neustar}
			PTR	`ns1.arcemus.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`indom30.indomco.fr`
			PTR	`ns1.ascio.net`
			PTR	`ns3.ascio.net`
			PTR	`dns1.cscdns.net`
			PTR	`pdns1.cscdns.net`
			PTR	`sbdns3.cscdns.net`
			PTR	`spdns3.cscdns.net`
			PTR	`ns0.netnames.net`
			PTR	`ns1.netnames.net`
			PTR	`ns3.netnames.net`
			PTR	`ns5.netnames.net`
			PTR	`ns7.netnames.net`
			PTR	`indom130.indomco.org`
			PTR	`ns2.domainnetwork.se`
			PTR	`ns.domainnetwork.se`
NS	`dns2.cscdns.net`
		A	2610:a1:1023::100^{🇺🇸 MAINT-ID-120082610:a1:1023::/48 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
		A	156.154.131.100^{🇺🇸 MAINT-ID-12008156.154.131.0/24 Neustar}
			PTR	`ns2.arcemus.com`
			PTR	`nusdns06.digitalarchives.com`
			PTR	`ns3.domainnetwork.com`
			PTR	`ns3.euro909.com`
			PTR	`indom80.indomco.hk`
			PTR	`ns2.ascio.net`
			PTR	`ns4.ascio.net`
			PTR	`dns2.cscdns.net`
			PTR	`pdns2.cscdns.net`
			PTR	`indom20.indomco.net`
			PTR	`ns2.netnames.net`
			PTR	`ns4.netnames.net`
			PTR	`ns6.netnames.net`
			PTR	`ns8.netnames.net`
MX	`yalesecurity-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f90c::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr03cu00100.inbound.protection.outlook.com`
		A	52.101.41.21^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00305.inbound.protection.outlook.com`
		A	52.101.41.180^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
		A	52.101.194.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
TXT	`MS=ms23992166`
TXT	`MS=5074EA7CE8401E29EE6EFC7ECFDB8D0D58DF5070`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`b/y/RO36smaUQ6AIe+u7empUNYwoCu73t4zPpiPy+QAGr9vYtLxTuLRT6/KJzUe5sLowFtF2dHHmt...`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2024-07-12 #2

`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=1776040182

WOT: SAFE (68/100)

Subdomains

neptune.yalesecurity.com

pluto.yalesecurity.com

uranus.yalesecurity.com

Same first word

yalesecurity.com

yalesecurity.org

yalesecurity.net

DNS History

9 records (4 active, 5 former)

●NSdns1.cscdns.net2026-03-05 → 2026-04-13 · 3 obs

○ 2018-01-29 04:27:10
● 2026-03-05 00:07:46
● 2026-04-13 00:36:30

●NSdns2.cscdns.net2026-03-05 → 2026-04-13 · 3 obs

○ 2018-01-29 04:27:10
● 2026-03-05 00:07:46
● 2026-04-13 00:36:30

○NSneptune.yalesecurity.com2015-06-11 → 2018-01-29 · 4 obs

● 2015-06-11 11:07:12
● 2018-01-29 04:27:10
○ 2026-03-05 00:07:46
○ 2026-04-13 00:36:30

○NSpluto.yalesecurity.com2015-06-11 → 2018-01-29 · 4 obs

● 2015-06-11 11:07:12
● 2018-01-29 04:27:10
○ 2026-03-05 00:07:46
○ 2026-04-13 00:36:30

○NSuranus.yalesecurity.com2015-06-11 → 2018-01-29 · 4 obs

● 2015-06-11 11:07:12
● 2018-01-29 04:27:10
○ 2026-03-05 00:07:46
○ 2026-04-13 00:36:30

○MXcust28558-1.in.mailcontrol.com2015-06-11 → 2018-01-29 · 4 obs

● 2015-06-11 11:07:12
● 2018-01-29 04:27:10
○ 2026-03-05 00:07:46
○ 2026-04-13 00:36:30

○MXcust28558-2.in.mailcontrol.com2015-06-11 → 2018-01-29 · 4 obs

● 2015-06-11 11:07:12
● 2018-01-29 04:27:10
○ 2026-03-05 00:07:46
○ 2026-04-13 00:36:30

●MXyalesecurity-com.mail.protection.outlook.com2026-03-05 → 2026-04-13 · 3 obs

○ 2018-01-29 04:27:10
● 2026-03-05 00:07:46
● 2026-04-13 00:36:30

●A12.231.185.542015-06-11 → 2026-04-13 · 2 obs

● 2015-06-11 11:07:12
● 2026-04-13 00:36:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net...	-
yalesecurity.com	dns1.cscdns.net, dns2.cscdns.net	-

✅ Authoritative Response

Server:156.154.130.100

NS records: dns1.cscdns.net, dns2.cscdns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for yalesecurity.com (unsigned zone)

⏱️ Timing

Total: 210ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`12.231.185.54`
NS	2	`dns1.cscdns.net, dns2.cscdns.net`
MX	1	`yalesecurity-com.mail.protection.outlook`
TXT	4	`MS=ms23992166, MS=5074EA7CE8401E29EE6EFC7ECFDB8D0D58DF5...`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

Analysis

Hierarchy

yalesecurity.com is a parent of neptune.yalesecurity.com, pluto.yalesecurity.com and uranus.yalesecurity.com.

IP Addresses

yalesecurity.com points to a single IP number: 12.231.185.54.

Name Servers

yalesecurity.com is delegated to two name servers: dns1.cscdns.net and dns2.cscdns.net.

yalesecurity.com shares the same name server setup as other domains, for example cfawebcasts.net, down-with-lovemovie.com, 25daysofchristmas.info, bae-systems.app and capco.com.

yalesecurity.com at least partially shares name servers with other domains, for example 91.221.193.in-addr.arpa and blackberrymbna.com.

Host names with two IP numbers:

dns1.cscdns.net points to 2610:a1:1022::100 and 156.154.130.100

dns2.cscdns.net points to 2610:a1:1023::100 and 156.154.131.100

Mail Servers

yalesecurity.com is handled by a single mail server, yalesecurity-com.mail.protection.outlook.com.

Host name yalesecurity-com.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:c901::1, 2a01:111:f403:c922::2, 2a01:111:f403:c946::, 2a01:111:f403:f90c::, 52.101.41.21, 52.101.41.180, 52.101.42.18 and 52.101.194.0.

yalesecurity.com - robtex.com