lexdata.com.ar - dns.ninja
lexdata.com.ar
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.towebs.com ⚠️ Not in zone NS records | ||||||
| A | 200.80.43.100🇦🇷 IFXNETWORK-REGIONAL-AS200.80.42.0/23 IFX Networks | ||||||
| NS | ns2.towebs.com ⚠️ Not in zone NS records | ||||||
| A | 200.80.43.101🇦🇷 IFXNETWORK-REGIONAL-AS200.80.42.0/23 IFX Networks | ||||||
| NS | ns3.towebs.com ⚠️ Not in zone NS records | ||||||
| A | 200.80.43.103🇦🇷 IFXNETWORK-REGIONAL-AS200.80.42.0/23 IFX Networks | ||||||
com.ar
| DNSSEC | ⚠️ Not signed | ||||||
| NS | e.dns.ar ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a.lactld.org ⚠️ Not in parent delegation | ||||||
| NS | c.dns.ar ⚠️ Not in parent delegation | ||||||
| NS | d.dns.ar ⚠️ Not in parent delegation | ||||||
| NS | f.dns.ar ⚠️ Not in parent delegation | ||||||
| TXT | COM.AR zone generated atEpoch 1786579452localtime 2026-08-12T21:04:12-03:00GM... | ||||||
| SOA | e.dns.arnoc@nic.gob.ar 2026-08-12 #21 | ||||||
WOT: SAFE (50/100)
MX for
lexdata.com.ar |
Same first word
lexdata.es |
lexdata.ro |
lexdata.sk |
lexdata.co.ao |
lexdata.it |
lexdata.com.ar |
lexdata.com.au |
lexdata.de |
lexdata.eu |
lexdata.com.br |
lexdata.cz |
lexdata.net |
lexdata.org |
Similar names
DNS History
14 records (3 active, 11 former)
○NSns1.dnspoint.net2015-08-05 → 2017-08-14 · 4 obs
● 2017-08-14 15:53:30
○ 2026-02-18 18:05:46
○ 2026-08-13 01:08:54
○NSns1.lexdata.com.ar2015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
●NSns1.towebs.com2016-07-23 → 2026-08-13 · 3 obs
● 2016-07-23 06:47:26
● 2026-08-13 01:08:54
○NSns2.lexdata.com.ar2015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
●NSns2.towebs.com2016-07-23 → 2026-08-13 · 3 obs
● 2016-07-23 06:47:26
● 2026-08-13 01:08:54
○NSns3.lexdata.com.ar2015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
●NSns3.towebs.com2016-07-23 → 2026-08-13 · 3 obs
● 2016-07-23 06:47:26
● 2026-08-13 01:08:54
○NSns4.lexdata.com.ar2015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
○NSns4.towebs.com2016-07-23 → 2017-08-14 · 4 obs
● 2016-07-23 06:47:26
● 2017-08-14 15:53:30
○ 2026-08-13 01:08:54
○MXlexdata.com.ar2016-07-23 → 2017-08-14 · 4 obs
● 2016-07-23 06:47:26
● 2017-08-14 15:53:30
○ 2026-08-13 01:08:54
○MXmail.lexdata.com.ar2015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
○A190.61.250.1802016-07-23 → 2017-08-14 · 5 obs
● 2016-07-23 06:47:26
● 2017-08-14 15:53:30
○ 2026-02-18 18:05:46
○ 2026-08-13 01:08:54
○A200.80.43.1402026-02-18 → 2026-02-18 · 3 obs
● 2026-02-18 18:05:46
○ 2026-08-13 01:08:54
○A216.59.32.1772015-08-05 → 2016-04-14 · 4 obs
● 2016-04-14 00:47:26
○ 2016-07-23 06:47:26
○ 2026-08-13 01:08:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ar | c.dns.ar, d.dns.ar, e.dns.ar, f.dns.ar | - |
| lexdata.com.ar | ns2.towebs.com, ns3.towebs.com, ns1.towebs.com | - |
✅ Authoritative Response
Server:200.80.43.100
NS records: ns2.towebs.com, ns3.towebs.com, ns1.towebs.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for lexdata.com.ar (unsigned zone)
⏱️ Timing
Total: 4737ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 200.80.43.140 |
| NS | 4 | ns1.towebs.com, ns2.towebs.com... |
| MX | 1 | lexdata.com.ar (pri: 0) |
| TXT | 1 | v=spf1 ip4:200.80.43.140 +a +mx +ip4:181 |
| SOA | 1 | ns1.towebs.com alertascpanel.towebs.com |
Analysis
Mail Server Role
The MX record for lexdata.com.ar points back to lexdata.com.ar — it is its own mail server.
Name Servers
The authoritative name servers for lexdata.com.ar are ns1.towebs.com, ns2.towebs.com and ns3.towebs.com — three in total.
lexdata.com.ar has at least partial name server overlap with other domains, such as shangri-la.com.ar, iscm.edu.ar, clienting.com.ar and two others.
These name servers tend to appear together with the name servers ns4.towebs.com, ns1.dnspoint.net and ns2.dnspoint.net.
The hostnames ns1.towebs.com, ns2.towebs.com and ns3.towebs.com each resolve to a single IP: ns1.towebs.com → 200.80.43.100, ns2.towebs.com → 200.80.43.101, ns3.towebs.com → 200.80.43.103.