kupol.space - robtex.com
kupol.space
| DNSSEC | โ ๏ธ Not signed | ||||||
| NS | ns1.beget.com โ ๏ธ Not in zone NS records | ||||||
| A | 93.92.81.0 | ||||||
| NS | ns2.beget.com โ ๏ธ Not in zone NS records | ||||||
| A | 185.50.27.12๐ท๐บ BEGET-AS185.50.27.0/24 BEGET.RU | ||||||
| PTR | ns2.beget.com | ||||||
space
| DNSSEC | ๐ Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com โญ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1786904930 | ||||||
Same first word
kupol.group |
kupol.tv |
kupol.kiev.ua |
kupol.com.ua |
kupol.info |
kupol.co |
kupol.space |
kupol.pro |
kupol.ru |
kupol.org |
kupol.net |
kupol.de |
kupol.su |
kupol.kz |
kupol.ca |
kupol.kr.ua |
Similar names
DNS History
2 records (2 active, 0 former)
๐ DNS Trace
๐ Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| space | ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.com, ns01.trs-dns.net | 8 records |
| kupol.space | ns2.beget.com, ns1.beget.com | - |
โ Authoritative Response
Server:93.92.81.0
NS records: ns2.beget.com, ns1.beget.com
๐ DNSSEC Status
โ ๏ธ Insecure (no DNSSEC)
No DS record for kupol.space (unsigned zone)
โฑ๏ธ Timing
Total: 764ms | Queries: -
๐ Records
| Type | Count | Sample Data |
|---|
๐ Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.net...)
Analysis
Name Servers
kupol.space uses two name servers for its delegation: ns1.beget.com and ns2.beget.com.
kupol.space shares its name server setup with other domains, including asdac.md, nasosural.ru, karasew.ru and two others.
kupol.space partially shares its NS delegation with several other domains, including audiotechnics.ru, devinotelecom.ru, u-dachny.ru and two others.
The name servers ns1.beget.pro, ns2.beget.pro, ns1.beget.ru and ns2.beget.ru are often found in use alongside these name servers.
ns1.beget.com resolves to 93.92.81.0. ns2.beget.com resolves to 185.50.27.12. Both host names point to a single IP number.