mail.maybemalware.com - robtex.com
mail.maybemalware.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 64.29.17.1🇺🇸 Amazon64.29.17.0/24 EC2 Prefix | ||||||
| A | 64.29.17.65🇺🇸 Amazon64.29.17.0/24 EC2 Prefix | ||||||
maybemalware.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 64.29.17.65🇺🇸 Amazon64.29.17.0/24 EC2 Prefix | ||||||
| A | 216.198.79.65🇺🇸 Amazon216.198.79.0/24 EC2 Prefix | ||||||
| NS | ns1.vercel-dns.com ⭐ | ||||||
| NS | ns2.vercel-dns.com | ||||||
| MX | maybemalware-com.mail.protection.outlook.com ⭐ | ||||||
| TXT | MS=ms17023842 | ||||||
| TXT | v=spf1 include:spf.protection.outlook.com -all | ||||||
| SOA | ns1.vercel-dns.comhostmaster@nsone.net serial=1753999595 | ||||||
Previously MX for
Same first word
Similar names
DNS History
3 records (2 active, 1 former)
●A64.29.17.12026-07-18 → 2026-07-18 · 2 obs
○ 2019-01-26 13:52:08
● 2026-07-18 18:48:42
● 2026-07-18 18:48:42
●A64.29.17.652026-07-18 → 2026-07-18 · 2 obs
○ 2019-01-26 13:52:08
● 2026-07-18 18:48:42
● 2026-07-18 18:48:42
○A79.243.170.2262019-01-26 → 2019-01-26 · 2 obs
● 2019-01-26 13:52:08
○ 2026-07-18 18:48:42
○ 2026-07-18 18:48:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| maybemalware.com | ns1.vercel-dns.com, ns2.vercel-dns.com | 4 records |
✅ Authoritative Response
Server:198.51.44.13
NS records: ns1.vercel-dns.com, ns2.vercel-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for maybemalware.com (unsigned zone)
⏱️ Timing
Total: 122ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 216.198.79.1, 216.198.79.65 |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.vercel-dns.com, ns1.vercel-dns.com, ns2.vercel-dns.com...)
Analysis
IP Addresses
mail.maybemalware.com has two IP addresses: 64.29.17.1 and 64.29.17.65
Additional host names — mail.lachopin.com, placepack.top, noxdom.com and two others — share IP numbers with mail.maybemalware.com.