protonalert.com - robtex.com
protonalert.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.r01.ru ⭐ | ||||||
| A | 31.177.80.41🇷🇺 RU-CENTER31.177.80.0/24 -NETWORK | ||||||
| PTR | ns1.r01.ru | ||||||
| NS | ns2.r01.ru | ||||||
| A | 31.177.76.41🇷🇺 RU-CENTER31.177.76.0/24 RU-SERVICE-NETWORK | ||||||
| PTR | ns2.r01.ru | ||||||
| SOA | ns1.r01.rusupport@r01.ru 2026-04-13 #3 | ||||||
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=1776844502 | ||||||
Same first word
protonalert.com |
Similar names
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| protonalert.com | ns1.r01.ru, ns2.r01.ru | - |
✅ Authoritative Response
Server:31.177.76.41
NS records: ns1.r01.ru, ns2.r01.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for protonalert.com (unsigned zone)
⏱️ Timing
Total: 1185ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.r01.ru, ns2.r01.ru |
| SOA | 1 | ns1.r01.ru support.r01.ru |
Analysis
Name Servers
protonalert.com's delegation uses two name servers, ns1.r01.ru and ns2.r01.ru.
protonalert.com shares the same name server setup as other domains, for example entest.ru, hopt.ru, levichevpartners.ru, timeu.ru and ruradio.ru.
protonalert.com shares some name servers with other domains, such as teachme.ru, aliusart.ru, chopin.ru and trafff.ru.
Host names with a single IP:
ns1.r01.ru points to 31.177.80.41.
ns2.r01.ru points to 31.177.76.41.