opalss.com - dns.ninja
opalss.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 178.62.102.213🇬🇧 DIGITALOCEAN178.62.64.0/18 DigitalOcean | ||||||
| NS | ns1.domain.com ⭐ | ||||||
| A | 172.64.52.73🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.domain.com | ||||||
| A | 172.64.53.117🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | NS1.DOMAIN.comdnsadmin@domain@com serial=125011002 | ||||||
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=1782135615 | ||||||
Previously MX for
opalss.com |
Same first word
opalss.com |
Similar names
DNS History
7 records (3 active, 4 former)
○NSns1.bluehost.com2017-08-14 → 2017-08-14 · 3 obs
○ 2026-03-14 09:27:36
○ 2026-06-22 13:43:46
●NSns1.domain.com2026-03-14 → 2026-06-22 · 3 obs
● 2026-03-14 09:27:36
● 2026-06-22 13:43:46
○NSns2.bluehost.com2017-08-14 → 2017-08-14 · 3 obs
○ 2026-03-14 09:27:36
○ 2026-06-22 13:43:46
●NSns2.domain.com2026-03-14 → 2026-06-22 · 3 obs
● 2026-03-14 09:27:36
● 2026-06-22 13:43:46
○MXopalss.com2017-08-14 → 2017-08-14 · 3 obs
○ 2026-03-14 09:27:36
○ 2026-06-22 13:43:46
○A108.179.213.752017-08-14 → 2017-08-14 · 3 obs
○ 2026-03-14 09:27:36
○ 2026-06-22 13:43:46
●A178.62.102.2132026-03-14 → 2026-06-22 · 3 obs
● 2026-03-14 09:27:36
● 2026-06-22 13:43:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| opalss.com | ns2.domain.com, ns1.domain.com | 2 records |
✅ Authoritative Response
Server:172.64.53.117
NS records: ns2.domain.com, ns1.domain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for opalss.com (unsigned zone)
⏱️ Timing
Total: 361ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 178.62.102.213 |
| NS | 2 | ns2.domain.com, ns1.domain.com |
| SOA | 1 | NS1.DOMAIN.com dnsadmin@domain.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.domain.com, ns1.domain.com)
Analysis
IP Addresses
opalss.com has exactly one IP address — 178.62.102.213.
Name Servers
opalss.com is served by two delegated name servers, ns1.domain.com and ns2.domain.com.
The name server configuration of opalss.com is shared with other domains, for instance thesaifigroup.com, nurnberg.band, corkinsole.com and two others.
The name servers of opalss.com overlap at least partially with those of other domains — among them projectupstart.org, kcms18.com, bryantdunbar.com and two more.
The name servers ns3.domain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com are commonly seen alongside these name servers.
Both ns1.domain.com and ns2.domain.com have a single IP address each — ns1.domain.com resolves to 172.64.52.73 while ns2.domain.com resolves to 172.64.53.117.