mx2.crypta.com - dns.ninja
mx2.crypta.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 185.65.56.186🇫🇷 NAMESHIELD185.65.56.0/22 Nameshield Paris Equinix-Overlap | ||||||
| PTR | mx1b.validname.com | ||||||
crypta.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 185.127.6.235🇫🇷 BLUECOM185.127.4.0/22 | ||||||
| NS | dns1.namebay.com ⭐ | ||||||
| NS | dns2.namebay.com | ||||||
| MX | mx01.cloud.vadesecure.com ⭐ | ||||||
| MX | mx02.cloud.vadesecure.com(20) | ||||||
| MX | mx03.cloud.vadesecure.com(30) | ||||||
| MX | mx04.cloud.vadesecure.com(40) | ||||||
| TXT | v=spf1 include:bluecom.fr -all | ||||||
| SOA | dns1.namebay.comadmin@validname.com 2025-12-15 #12 | ||||||
Previously MX for
Same first word
Similar names
DNS History
2 records (1 active, 1 former)
●A185.65.56.1862026-03-25 → 2026-07-23 · 3 obs
○ 2016-12-25 18:18:26
● 2026-03-25 07:05:06
● 2026-07-23 20:41:18
● 2026-03-25 07:05:06
● 2026-07-23 20:41:18
○A185.65.56.1912015-05-16 → 2016-12-25 · 4 obs
● 2015-05-16 02:19:40
● 2016-12-25 18:18:26
○ 2026-03-25 07:05:06
○ 2026-07-23 20:41:18
● 2016-12-25 18:18:26
○ 2026-03-25 07:05:06
○ 2026-07-23 20:41:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| crypta.com | dns1.namebay.com, dns2.namebay.com | 8 records |
✅ Authoritative Response
Server:185.65.56.134
NS records: dns1.namebay.com, dns2.namebay.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for crypta.com (unsigned zone)
⏱️ Timing
Total: 245ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.65.56.186 |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (dns1.namebay.com, dns1.namebay.com, dns1.namebay.com...)
Analysis
IP Addresses
mx2.crypta.com resolves to just one IP address, 185.65.56.186.
Two other host names, along with mx2.chankan.com, _dc-mx.a113addb521d.easy-communication.fr and mx2.sandaya.ru, also share IP numbers with mx2.crypta.com.