`server2.isilicom.com.mx`

DNSSEC	⚠️ Not signed
A	143.255.58.58^{🇲🇽 DimeNOC143.255.56.0/22 Proxy-registered route object}
		PTR	`server2.isilicom.com.mx`
NS	`ns1.isilicom.com.mx` ⭐ ⚠️ Not in parent delegation
		A	143.255.58.58^{🇲🇽 DimeNOC143.255.56.0/22 Proxy-registered route object}
			PTR	`server2.isilicom.com.mx`
NS	`ns2.isilicom.com.mx` ⚠️ Not in parent delegation
		A	143.255.58.58^{🇲🇽 DimeNOC143.255.56.0/22 Proxy-registered route object}
			PTR	`server2.isilicom.com.mx`
MX	`server2.isilicom.com.mx` ⭐
		A	143.255.58.58^{🇲🇽 DimeNOC143.255.56.0/22 Proxy-registered route object}
			PTR	`server2.isilicom.com.mx`
TXT	`v=spf1 +mx +a +ip4:143.255.58.58 ~all`
SOA	`ns1.isilicom.com.mx`root@server2.isilicom.com.mx 2026-02-09 #0

`isilicom.com.mx`

	DNSSEC	⚠️ Not signed
	A	143.255.58.58^{🇲🇽 DimeNOC143.255.56.0/22 Proxy-registered route object}
	NS	`dns32526.dizinc.com` ⭐ ⚠️ Not in parent delegation
	NS	`dns32527.dizinc.com` ⚠️ Not in parent delegation
	NS	`ns1.isilicom.com.mx` ⚠️ Not in zone NS records
	NS	`ns2.isilicom.com.mx` ⚠️ Not in zone NS records
	MX	`isilicom.com.mx` ⭐
	TXT	`v=spf1 ip4:143.255.58.58 +a +mx +ip4:138.128.182.218 -all`
	SOA	`dns32526.dizinc.com`root@server2.isilicom.com.mx 2026-03-06 #0

PTR for

58.58.255.143.in-addr.arpa

MX for

server2.isilicom.com.mx

Same first word

Similar names

2server.ru

2server.org

2server.com

DNS History

4 records (4 active, 0 former)

●NSns1.isilicom.com.mx2026-03-21 → 2026-03-26 · 2 obs

● 2026-03-21 06:23:14
● 2026-03-26 15:47:02

●NSns2.isilicom.com.mx2026-03-21 → 2026-03-26 · 2 obs

● 2026-03-21 06:23:14
● 2026-03-26 15:47:02

●MXserver2.isilicom.com.mx2026-03-21 → 2026-03-26 · 2 obs

● 2026-03-21 06:23:14
● 2026-03-26 15:47:02

●A143.255.58.582026-03-21 → 2026-03-26 · 2 obs

● 2026-03-21 06:23:14
● 2026-03-26 15:47:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx...	-
isilicom.com.mx	ns1.isilicom.com.mx, ns2.isilicom.com.mx	2 records

✅ Authoritative Response

Server:143.255.58.60

NS records: ns1.isilicom.com.mx, ns2.isilicom.com.mx

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for isilicom.com.mx (unsigned zone)

⏱️ Timing

Total: 249ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`143.255.58.58`
NS	2	`ns2.isilicom.com.mx, ns1.isilicom.com.mx`
MX	1	`server2.isilicom.com.mx (pri: 0)`
TXT	1	`v=spf1 +mx +a +ip4:143.255.58.58 ~all`
SOA	1	`ns1.isilicom.com.mx root.server2.isilico`

📌 Glue Records Collected

Total: 2

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

Analysis

Mail Server Role

server2.isilicom.com.mx serves as the mail server for server2.isilicom.com.mx.

IP Addresses

server2.isilicom.com.mx points to IP number: 143.255.58.58.

Other host names such as isilicom.com.mx, ns1.isilicom.com.mx, server.isilicom.com.mx, basta.com.mx and sisemhlconsultores.com.mx share IPs with server2.isilicom.com.mx.

Name Servers

server2.isilicom.com.mx is delegated to two name servers: ns1.isilicom.com.mx and ns2.isilicom.com.mx.

server2.isilicom.com.mx uses the same name server setup as other domains, for example sage.com.mx.

server2.isilicom.com.mx at least partially shares name servers with other domains, for instance basta.com.mx, sisemhlconsultores.com.mx, hotelazteca.com.mx, clinicaegurrola.com.mx and satab.mx.

These name servers are commonly used with dns32526.dizinc.com and dns32527.dizinc.com.

Host names sharing one IP: ns1.isilicom.com.mx and ns2.isilicom.com.mx point to 143.255.58.58.

Mail Servers

server2.isilicom.com.mx is handled by a single mail server, server2.isilicom.com.mx.

server2.isilicom.com.mx points to a single IP: 143.255.58.58.

server2.isilicom.com.mx - robtex.com