🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`luxurycollection.mx`

DNSSEC	⚠️ Not signed
A	3.214.21.245^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-214-21-245.compute-1.amazonaws.com`
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	`ns5.bac.com`
			PTR	`kandns06.digitalarchives.com`
			PTR	`ns1.euro909.com`
			PTR	`ns2.euro909.com`
			PTR	`indom10.indomco.com`
			PTR	`g.ns-bac.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	`ns9.bac.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`
			PTR	`h.ns-bac.org`
TXT	`v=spf1 -all`
SOA	`dns1.cscdns.net`hostmaster@cscdns.net 2017-09-28 #8

`mx`

	DNSSEC	🔒 Signed (DS record present)
	NS	`m.mx-ns.mx` ⭐
	NS	`c.mx-ns.mx`
	NS	`e.mx-ns.mx`
	NS	`i.mx-ns.mx`
	NS	`o.mx-ns.mx`
	NS	`x.mx-ns.mx`
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1786931136

Same first word

DNS History

12 records (3 active, 9 former)

●NSdns1.cscdns.net2018-09-17 → 2026-08-17 · 3 obs

○ 2017-02-09 07:06:34
● 2018-09-17 14:13:30
● 2026-08-17 01:58:30

●NSdns2.cscdns.net2018-09-17 → 2026-08-17 · 3 obs

○ 2017-02-09 07:06:34
● 2018-09-17 14:13:30
● 2026-08-17 01:58:30

○NSns1.netnames.net2015-07-19 → 2017-02-09 · 4 obs

● 2015-07-19 07:51:44
● 2017-02-09 07:06:34
○ 2018-09-17 14:13:30
○ 2026-08-17 01:58:30

○NSns2.netnames.net2015-07-19 → 2017-02-09 · 4 obs

● 2015-07-19 07:51:44
● 2017-02-09 07:06:34
○ 2018-09-17 14:13:30
○ 2026-08-17 01:58:30

○NSns5.netnames.net2015-07-19 → 2017-02-09 · 4 obs

● 2015-07-19 07:51:44
● 2017-02-09 07:06:34
○ 2018-09-17 14:13:30
○ 2026-08-17 01:58:30

○NSns6.netnames.net2015-07-19 → 2017-02-09 · 4 obs

● 2015-07-19 07:51:44
● 2017-02-09 07:06:34
○ 2018-09-17 14:13:30
○ 2026-08-17 01:58:30

○MXrelay1.netnames.net2015-07-19 → 2018-09-17 · 4 obs

● 2015-07-19 07:51:44
● 2018-09-17 14:13:30
○ 2026-08-10 22:38:12
○ 2026-08-17 01:58:30

○MXrelay2.netnames.net2015-07-19 → 2018-09-17 · 4 obs

● 2015-07-19 07:51:44
● 2018-09-17 14:13:30
○ 2026-08-10 22:38:12
○ 2026-08-17 01:58:30

○A165.160.13.202018-09-17 → 2018-09-17 · 4 obs

○ 2017-02-09 07:06:34
● 2018-09-17 14:13:30
○ 2026-08-10 22:38:12
○ 2026-08-17 01:58:30

○A165.160.15.202018-09-17 → 2018-09-17 · 4 obs

○ 2017-02-09 07:06:34
● 2018-09-17 14:13:30
○ 2026-08-10 22:38:12
○ 2026-08-17 01:58:30

○A185.26.230.1292015-07-19 → 2017-02-09 · 4 obs

● 2015-07-19 07:51:44
● 2017-02-09 07:06:34
○ 2018-09-17 14:13:30
○ 2026-08-17 01:58:30

●A3.214.21.2452026-08-10 → 2026-08-17 · 3 obs

○ 2018-09-17 14:13:30
● 2026-08-10 22:38:12
● 2026-08-17 01:58:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
luxurycollection.mx	dns1.cscdns.net, dns2.cscdns.net	-

✅ Authoritative Response

Server:156.154.131.100

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for luxurycollection.mx (unsigned zone)

⏱️ Timing

Total: 2016ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.214.21.245`
NS	2	`dns1.cscdns.net, dns2.cscdns.net`
TXT	1	`v=spf1 -all`
SOA	1	`dns1.cscdns.net hostmaster.cscdns.net`

Analysis

IP Addresses

luxurycollection.mx points to a single IP number: 3.214.21.245.

Additional host names — fourpointsnewyorkdowntown.com, westincleveland.com, westinsavannah.com and two others — share IP numbers with luxurycollection.mx.

Name Servers

Two name servers handle the delegation for luxurycollection.mx: dns1.cscdns.net and dns2.cscdns.net.

luxurycollection.mx shares its name server setup with other domains, including paladine.com, digitalcamera.nyc, abouttimerolex.com and two others.

luxurycollection.mx has overlapping name servers with several other domains — among them bage.dk, paramountmortgagellc.com, merilledg.net and merilledg.com.

These name servers commonly appear alongside the name servers ns101.bac.com and ns102.bac.com.

dns1.cscdns.net and dns2.cscdns.net both carry two IP addresses. The A records for dns1.cscdns.net are 156.154.130.100 and 2610:a1:1022::100; the A records for dns2.cscdns.net are 156.154.131.100 and 2610:a1:1023::100.

luxurycollection.mx - robtex.com