descovystinks.net - robtex.com
descovystinks.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=1786878279 | ||||||
Same first word
descovystinks.info |
descovystinks.net |
DNS History
9 records (8 active, 1 former)
●NSns1.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●NSns2.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●NSns5.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●NSns6.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●MXrelay1.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●MXrelay2.netnames.net2017-01-04 → 2026-08-16 · 2 obs
● 2026-08-16 11:20:02
●A165.160.13.202019-12-30 → 2026-08-16 · 3 obs
● 2019-12-30 20:56:46
● 2026-08-16 11:20:02
●A165.160.15.202019-12-30 → 2026-08-16 · 3 obs
● 2019-12-30 20:56:46
● 2026-08-16 11:20:02
○A185.26.230.1292017-01-04 → 2017-01-04 · 3 obs
○ 2019-12-30 20:56:46
○ 2026-08-16 11:20:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | k.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net... | - |
| descovystinks.net | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | 8 records |
✅ Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for descovystinks.net (unsigned zone)
⏱️ Timing
Total: 1387ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.15.20, 165.160.13.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| TXT | 1 | v=spf1 -all |
| 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
descovystinks.net resolves to the IP addresses 165.160.13.20 and 165.160.15.20
stjude.net, compreesaque.com.br, embecta.hn plus two other host names have IP numbers in common with descovystinks.net.
Name Servers
Four name servers handle the delegation for descovystinks.net: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
descovystinks.net partially shares its NS delegation with several other domains, including dunedinsmaller.co.uk, koodza.cn, passengerexperienceweek.com and two others.
These name servers are regularly seen alongside ns7.netnames.net and ns8.netnames.net as name servers.
Each of ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net resolves to two IP numbers, falling into two groups: ns1.netnames.net and ns5.netnames.net share 156.154.130.100 and 2610:a1:1022::100, while ns2.netnames.net and ns6.netnames.net share 156.154.131.100 and 2610:a1:1023::100.
Both ns1.netnames.net and ns5.netnames.net resolve to 2610:a1:1022::100 IP addresses each.
Both ns1.netnames.net and ns5.netnames.net resolve to 156.154.130.100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 2610:a1:1023::100 IP addresses each.
Both ns2.netnames.net and ns6.netnames.net resolve to 156.154.131.100 IP addresses each.
Mail Servers
descovystinks.net uses two mail servers, relay1.netnames.net and relay2.netnames.net.
The mail server setup of descovystinks.net matches that of other domains such as nwolb.biz, allianz-global-assistance-travel-aid.com, mostchosenbrands.com and two others.
At least a portion of descovystinks.net's mail servers are also used by other domains, for example dunlopsafety.com.
relay1.netnames.net resolves to 185.26.230.83. relay2.netnames.net resolves to 185.26.230.89. Both host names point to a single IP number.