🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`uswest1.snappcms.com`

CNAME	`snappcms.com`
DNSSEC	⚠️ Not signed
A	3.3.3.145^{🇺🇸 Amazon3.3.3.0/24 EC2 Prefix}
NS	`ns1-71.azure-dns.com` ⭐ ⚠️ Not in parent delegation
		A	2603:1061:0:10::47^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-71.azure-dns.com`
		A	150.171.10.71^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-71.azure-dns.com`
NS	`ns1.snappcms.com` ⚠️ Not in zone NS records
NS	`ns2-71.azure-dns.net` ⚠️ Not in parent delegation
		A	2620:1ec:8ec:10::47^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-71.azure-dns.net`
		A	150.171.16.71^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-71.azure-dns.net`
NS	`ns2.snappcms.com` ⚠️ Not in zone NS records
NS	`ns3-71.azure-dns.org` ⚠️ Not in parent delegation
		A	2a01:111:4000:10::47^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-71.azure-dns.org`
		A	13.107.222.71^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-71.azure-dns.org`
NS	`ns4-71.azure-dns.info` ⚠️ Not in parent delegation
		A	2620:1ec:bda:10::47^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-71.azure-dns.info`
		A	13.107.206.71^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-71.azure-dns.info`
MX	`mx.snappcms.com` ⭐
		A	3.3.3.145^{🇺🇸 Amazon3.3.3.0/24 EC2 Prefix}
TXT	`v=spf1 a:dns.snappcms.com ~all`
SOA	`ns1-71.azure-dns.com`support@cloudns.net serial=1914052231

`snappcms.com`

	DNSSEC	⚠️ Not signed
	A	3.3.3.145^{🇺🇸 Amazon3.3.3.0/24 EC2 Prefix}
	NS	`ns1-71.azure-dns.com` ⭐ ⚠️ Not in parent delegation
	NS	`ns1.snappcms.com` ⚠️ Not in zone NS records
	NS	`ns2-71.azure-dns.net` ⚠️ Not in parent delegation
	NS	`ns2.snappcms.com` ⚠️ Not in zone NS records
	NS	`ns3-71.azure-dns.org` ⚠️ Not in parent delegation
	NS	`ns4-71.azure-dns.info` ⚠️ Not in parent delegation
	MX	`mx.snappcms.com` ⭐
	TXT	`v=spf1 a:dns.snappcms.com ~all`
	SOA	`ns1-71.azure-dns.com`support@cloudns.net serial=1914052231

PTR for

199.135.236.204.in-addr.arpa

DNS History

2 records (1 active, 1 former)

○A204.236.135.1992014-12-27 → 2016-05-03 · 4 obs

● 2014-12-27 11:34:30
● 2016-05-03 09:07:06
○ 2026-08-16 14:29:50
○ 2026-08-16 17:32:28

●CNAMEsnappcms.com2026-08-16 → 2026-08-16 · 2 obs

● 2026-08-16 14:29:50
● 2026-08-16 17:32:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, e.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
snappcms.com	ns1.snappcms.com, ns2.snappcms.com	2 records

✅ Authoritative Response

Server:51.161.192.78

NS records: ns1.snappcms.com, ns2.snappcms.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for snappcms.com (unsigned zone)

⏱️ Timing

Total: 759ms | Queries: -

📄 Records

Type	Count	Sample Data
CNAME	1	`snappcms.com`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.snappcms.com, ns2.snappcms.com)

Analysis

IP Addresses

uswest1.snappcms.com points to a single IP number: 3.3.3.145.

Other host names, among them mx.snappcms.com and snappcms.com, have IP numbers in common with uswest1.snappcms.com.

Name Servers

uswest1.snappcms.com is delegated to 6 name servers: ns1-71.azure-dns.com, ns1.snappcms.com, ns2.snappcms.com and 3 other.

At least some of uswest1.snappcms.com's name servers are shared with other domains, for example bourboninsider.net, moteld.com, appillinois.com and two more.

These name servers tend to co-occur with ns4-71.azure-dns.info, ns2-71.azure-dns.net, ns3-71.azure-dns.org and 7 other name servers in the same DNS delegations.

Four hostnames, each resolving to a pair of IP addresses: ns1-71.azure-dns.com directs to 150.171.10.71 and 2603:1061:0:10::47; ns4-71.azure-dns.info directs to 13.107.206.71 and 2620:1ec:bda:10::47; ns2-71.azure-dns.net directs to 150.171.16.71 and 2620:1ec:8ec:10::47; ns3-71.azure-dns.org directs to 13.107.222.71 and 2a01:111:4000:10::47.

Mail Servers

uswest1.snappcms.com has one mail server: mx.snappcms.com.

uswest1.snappcms.com shares its mail server setup with other domains, such as snappcms.com.

mx.snappcms.com resolves to a single IP number: 3.3.3.145.

uswest1.snappcms.com - robtex.com