problemskin.net - dns.ninja
problemskin.net
net
| 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=1782878586 | ||||||
Same first word
problemskin.com |
problemskin.net |
Similar names
DNS History
9 records (7 active, 2 former)
○NSdns1.emarkmonitor.com2007-09-17 → 2007-09-17 · 3 obs
○ 2015-06-24 13:28:38
○ 2026-07-01 04:07:08
○NSdns2.emarkmonitor.com2007-09-17 → 2007-09-17 · 3 obs
○ 2015-06-24 13:28:38
○ 2026-07-01 04:07:08
●NSns1.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●NSns2.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●NSns5.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●NSns6.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●MXrelay1.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●MXrelay2.netnames.net2015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
●A185.26.230.1292015-06-24 → 2026-07-01 · 3 obs
● 2015-06-24 13:28:38
● 2026-07-01 04:07:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| problemskin.net | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | 8 records |
✅ Authoritative Response
Server:156.154.130.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for problemskin.net (unsigned zone)
⏱️ Timing
Total: 281ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 185.26.230.129 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 100) |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns2.netnames.net, ns2.netnames.net, ns1.netnames.net...)
Analysis
IP Addresses
problemskin.net points to a single IP number: 185.26.230.129.
Additional host names — halifax-life.at, cantium.net, fastpoker.com and two others — share IP numbers with problemskin.net.
Name Servers
problemskin.net has four authoritative name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of problemskin.net overlap at least partially with those of other domains — among them tesashop.biz, ashmore.london, rossmann-fotowelt.com and two more.
ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net each have two IP addresses. Specifically, ns1.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100, ns2.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100, ns5.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100 and ns6.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100.
Host names pointing to 2610:a1:1022::100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 156.154.130.100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 2610:a1:1023::100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Host names pointing to 156.154.131.100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Mail Servers
problemskin.net has two mail servers: relay1.netnames.net and relay2.netnames.net.
problemskin.net shares the same mail server setup as other domains, including aibcapitalmarkets.ie, mcpsandprs.eu, moenbuilder.com and two others.
problemskin.net has mail servers in common with other domains — for example emaildriver.com, mercerdelta.com.tw and glitterboxibiza.com.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each — relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.