oopsdarn.com - dns.ninja
oopsdarn.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 174.114.43.167🇨🇦 ROGERS-CABLE-AS174.114.0.0/16 | ||||||
| PTR | pool-174-114-43-167.cpe.net.cable.rogers.com | ||||||
| NS | dns1.registrar-servers.com ⭐ | ||||||
| A | 2610:a1:1024::200🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar | ||||||
| PTR | dns1.namecheaphosting.com | ||||||
| PTR | dns1.registrar-servers.com | ||||||
| A | 156.154.132.200🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar | ||||||
| PTR | dns1.namecheaphosting.com | ||||||
| PTR | dns1.registrar-servers.com | ||||||
| NS | dns2.registrar-servers.com | ||||||
| A | 2610:a1:1025::200🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar | ||||||
| PTR | dns2.namecheaphosting.com | ||||||
| PTR | dns2.registrar-servers.com | ||||||
| A | 156.154.133.200🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar | ||||||
| PTR | dns2.namecheaphosting.com | ||||||
| PTR | dns2.registrar-servers.com | ||||||
| SOA | dns1.registrar-servers.comhostmaster@registrar-servers.com serial=1758782792 | ||||||
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=1782068390 | ||||||
Previously MX for
oopsdarn.com |
Same first word
oopsdarn.com |
Similar names
DNS History
7 records (3 active, 4 former)
●NSdns1.registrar-servers.com2026-03-06 → 2026-06-21 · 3 obs
● 2026-03-06 03:19:48
● 2026-06-21 19:00:52
●NSdns2.registrar-servers.com2026-03-06 → 2026-06-21 · 3 obs
● 2026-03-06 03:19:48
● 2026-06-21 19:00:52
○NSns4.lunarpages.com2015-07-06 → 2017-03-24 · 4 obs
● 2017-03-24 05:43:44
○ 2026-03-06 03:19:48
○ 2026-06-21 19:00:52
○NSns5.lunarpages.com2015-07-06 → 2017-03-24 · 4 obs
● 2017-03-24 05:43:44
○ 2026-03-06 03:19:48
○ 2026-06-21 19:00:52
○MXoopsdarn.com2015-07-06 → 2017-03-24 · 4 obs
● 2017-03-24 05:43:44
○ 2026-03-06 03:19:48
○ 2026-06-21 19:00:52
●A174.114.43.1672026-03-06 → 2026-06-21 · 3 obs
● 2026-03-06 03:19:48
● 2026-06-21 19:00:52
○A74.50.28.1952015-07-06 → 2017-03-24 · 4 obs
● 2017-03-24 05:43:44
○ 2026-03-06 03:19:48
○ 2026-06-21 19:00:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| oopsdarn.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for oopsdarn.com (unsigned zone)
⏱️ Timing
Total: 91ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 174.114.43.167 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
oopsdarn.com resolves to one IP address: 174.114.43.167.
Name Servers
The NS records for oopsdarn.com delegate to dns1.registrar-servers.com and dns2.registrar-servers.com.
oopsdarn.com uses the same name servers as several other domains — among them wealthjournal.org, palmdeserthotels.net, wellport.org and two more.
oopsdarn.com has at least partial name server overlap with other domains, such as oceanaccesswaterfront.com, retelab.net, charlescortes.com and two others.
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200. Likewise, dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200 — two IP addresses apiece.