🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`securitylog.cloud`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns65.domaincontrol.com` ⭐
NS	`ns66.domaincontrol.com`
MX	`smtp.secureserver.net` ⭐
		A	216.69.141.71^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp01-v01.prod.phx3.secureserver.net`
		A	216.69.141.84^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp02-v01.prod.phx3.secureserver.net`
		A	216.69.141.113^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp03-v01.prod.phx3.secureserver.net`
MX	`mailstore1.secureserver.net`⁽¹⁰⁾
		A	216.69.141.78^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp01-v02.prod.phx3.secureserver.net`
		A	216.69.141.114^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp03-v02.prod.phx3.secureserver.net`
		A	216.69.141.162^{🇺🇸 AS398101216.69.140.0/22}
			PTR	`osplibsmtp02-v02.prod.phx3.secureserver.net`
SOA	`ns65.domaincontrol.com`dns@jomax.net 2023-09-19 #0

`cloud`

	DNSSEC	⚠️ Not signed
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1793712929

DNS History

6 records (6 active, 0 former)

●NSns65.domaincontrol.com2026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

●NSns66.domaincontrol.com2026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

●MXmailstore1.secureserver.net2026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

●MXsmtp.secureserver.net2026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

●A15.197.148.332026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

●A3.33.130.1902026-09-08 → 2026-11-03 · 2 obs

● 2026-09-08 07:18:58
● 2026-11-03 14:20:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cloud	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
securitylog.cloud	ns65.domaincontrol.com, ns66.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.70.43

NS records: ns65.domaincontrol.com, ns66.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securitylog.cloud (unsigned zone)

⏱️ Timing

Total: 656ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns65.domaincontrol.com, ns66.domaincontrol.com`
MX	2	`mailstore1.secureserver.net (pri: 10), smtp.secureserver.net (pri: 0)`
SOA	1	`ns65.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)

Analysis

IP Addresses

securitylog.cloud resolves to the IP addresses 3.33.130.190 and 15.197.148.33

Name Servers

securitylog.cloud uses two name servers for its delegation: ns65.domaincontrol.com and ns66.domaincontrol.com.

Mail Servers

securitylog.cloud has two mail servers: mailstore1.secureserver.net and smtp.secureserver.net.

The host names mailstore1.secureserver.net and smtp.secureserver.net each point to three IP numbers: mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162. smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113.

securitylog.cloud - robtex.com