void.mx - robtex.com
void.mx
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-1442.awsdns-52.org ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5305:a200::1🇺🇸 Amazon2600:9000:5305::/48 - CloudFront | ||||||
| PTR | ns-1442.awsdns-52.org | ||||||
| A | 205.251.197.162🇺🇸 Amazon205.251.197.0/24 prefix | ||||||
| PTR | ns-1442.awsdns-52.org | ||||||
| NS | ns-1835.awsdns-37.co.uk ⚠️ Not in zone NS records | ||||||
| A | 2600:9000:5307:2b00::1🇺🇸 Amazon2600:9000:5307::/48 - CloudFront | ||||||
| PTR | ns-1835.awsdns-37.co.uk | ||||||
| A | 205.251.199.43🇺🇸 Amazon205.251.199.0/24 prefix | ||||||
| PTR | ns-1835.awsdns-37.co.uk | ||||||
| NS | ns1.yandexcloud.net | ||||||
| A | 2a0d:d6c1:0:1a::1b4🇷🇺 YandexCloud2a0d:d6c1::/32 | ||||||
| PTR | ns1.yandexcloud.net | ||||||
| A | 84.201.185.208🇷🇺 YandexCloud84.201.184.0/22 Yandex Cloud | ||||||
| PTR | ns1.yandexcloud.net | ||||||
| NS | ns2.yandexcloud.net | ||||||
| A | 2a0d:d6c1:0:1a::2c9🇷🇺 YandexCloud2a0d:d6c1::/32 | ||||||
| PTR | ns2.yandexcloud.net | ||||||
| A | 84.201.189.229🇷🇺 YandexCloud84.201.188.0/23 Yandex Cloud | ||||||
| PTR | ns2.yandexcloud.net | ||||||
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.mxhostmaster@nic.mx serial=1783224065 | ||||||
Same first word
Similar names
DNS History
9 records (4 active, 5 former)
○NSlocalhost2015-10-27 → 2016-04-18 · 4 obs
● 2016-04-18 00:26:40
○ 2017-02-03 02:15:18
○ 2026-07-05 04:37:46
●NSns-1442.awsdns-52.org2017-02-03 → 2026-07-05 · 3 obs
● 2017-02-03 02:15:18
● 2026-07-05 04:37:46
●NSns-1835.awsdns-37.co.uk2017-02-03 → 2026-07-05 · 3 obs
● 2017-02-03 02:15:18
● 2026-07-05 04:37:46
○NSns-226.awsdns-28.com2017-02-03 → 2020-12-23 · 5 obs
● 2017-02-03 02:15:18
● 2020-12-23 00:11:38
○ 2026-02-18 04:25:36
○ 2026-07-05 04:37:46
○NSns-752.awsdns-30.net2017-02-03 → 2020-12-23 · 5 obs
● 2017-02-03 02:15:18
● 2020-12-23 00:11:38
○ 2026-02-18 04:25:36
○ 2026-07-05 04:37:46
○NSns.void.mx2015-10-27 → 2016-04-18 · 4 obs
● 2016-04-18 00:26:40
○ 2017-02-03 02:15:18
○ 2026-07-05 04:37:46
●NSns1.yandexcloud.net2026-02-18 → 2026-07-05 · 3 obs
● 2026-02-18 04:25:36
● 2026-07-05 04:37:46
●NSns2.yandexcloud.net2026-02-18 → 2026-07-05 · 3 obs
● 2026-02-18 04:25:36
● 2026-07-05 04:37:46
○A103.56.218.1612015-10-27 → 2016-04-18 · 4 obs
● 2016-04-18 00:26:40
○ 2017-02-03 02:15:18
○ 2026-07-05 04:37:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| mx | c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx... | - |
| void.mx | ns-1835.awsdns-37.co.uk, ns1.yandexcloud.net, ns2.yandexcloud.net, ns-1442.awsdns-52.org | - |
✅ Authoritative Response
Server:205.251.197.162
NS records: ns-1835.awsdns-37.co.uk, ns1.yandexcloud.net, ns2.yandexcloud.net, ns-1442.awsdns-52.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for void.mx (unsigned zone)
⏱️ Timing
Total: 1225ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The NS records for void.mx point to four name servers: ns1.yandexcloud.net, ns2.yandexcloud.net, ns-1442.awsdns-52.org and ns-1835.awsdns-37.co.uk.
There is at least partial name server overlap between void.mx and other domains — wellhub.com, liferay.ru, d3divknv4im90z.cloudfront.net and two more among them.
All four hostnames — ns1.yandexcloud.net, ns2.yandexcloud.net, ns-1442.awsdns-52.org and ns-1835.awsdns-37.co.uk — resolve to two IP numbers apiece: ns1.yandexcloud.net to 84.201.185.208 and 2a0d:d6c1:0:1a::1b4; ns2.yandexcloud.net to 84.201.189.229 and 2a0d:d6c1:0:1a::2c9; ns-1442.awsdns-52.org to 205.251.197.162 and 2600:9000:5305:a200::1; ns-1835.awsdns-37.co.uk to 205.251.199.43 and 2600:9000:5307:2b00::1.