likelywrong.com - dns.ninja
likelywrong.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1790171264 | ||||||
Same first word
likelywrong.com |
Previous names
Next names
DNS History
7 records (6 active, 1 former)
●NSns63.domaincontrol.com2015-05-18 → 2026-09-23 · 2 obs
● 2026-09-23 14:06:28
●NSns64.domaincontrol.com2015-05-18 → 2026-09-23 · 2 obs
● 2026-09-23 14:06:28
●MXmailstore1.secureserver.net2015-05-18 → 2026-09-23 · 2 obs
● 2026-09-23 14:06:28
●MXsmtp.secureserver.net2015-05-18 → 2026-09-23 · 2 obs
● 2026-09-23 14:06:28
●A15.197.148.332026-09-04 → 2026-09-23 · 3 obs
● 2026-09-04 19:49:34
● 2026-09-23 14:06:28
○A184.168.221.622015-05-18 → 2017-07-06 · 4 obs
● 2017-07-06 00:17:42
○ 2026-09-04 19:49:34
○ 2026-09-23 14:06:28
●A3.33.130.1902026-09-04 → 2026-09-23 · 3 obs
● 2026-09-04 19:49:34
● 2026-09-23 14:06:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net, m.gtld-servers.net... | - |
| likelywrong.com | ns63.domaincontrol.com, ns64.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.101.42
NS records: ns63.domaincontrol.com, ns64.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for likelywrong.com (unsigned zone)
⏱️ Timing
Total: 156ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns63.domaincontrol.com, ns64.domaincontrol.com |
| MX | 2 | mailstore1.secureserver.net (pri: 10), smtp.secureserver.net (pri: 0) |
| SOA | 1 | ns63.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns63.domaincontrol.com, ns63.domaincontrol.com, ns64.domaincontrol.com...)
Analysis
IP Addresses
likelywrong.com has two IP addresses: 3.33.130.190 and 15.197.148.33
vanitycloseouts.com, ecloudconcierge.com, lenscut.in plus two other host names have IP numbers in common with likelywrong.com.
Name Servers
DNS delegation for likelywrong.com points to two name servers: ns63.domaincontrol.com and ns64.domaincontrol.com.
The name server configuration of likelywrong.com is shared with other domains, for instance emberbleuprovisions.com, fldata.com, sheldonslewis.com and two others.
ns63.domaincontrol.com directs to 97.74.101.42 and 2603:5:2154::2a. ns64.domaincontrol.com directs to 173.201.69.42 and 2603:5:2254::2a. Each host name carries two IP addresses.
Mail Servers
likelywrong.com uses two mail servers, mailstore1.secureserver.net and smtp.secureserver.net.
The mail server setup of likelywrong.com matches that of other domains such as bestorthopedicsurgeonprescott.com, allisonhayesspeaks.com, couturebeautylabs.com and two others.
The mail servers for likelywrong.com overlap at least partially with those of other domains, including elk-intl.com and theboywithangelman.io.
Both mailstore1.secureserver.net and smtp.secureserver.net point to three IP numbers: mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162, while smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113.