ns2.wntelecom.net.br RRSIG records

RRSIG
1h
A 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. LzbVj17btLrTnlEJHqYRax3J11mcPXk71j0A7k/1fJVyRZTV6FRtuV00wT3eV8V4YFZxkbjvynALtZ3QnFNvSw==
AAAA 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. sdeoa6uBqUVT9fHZo10rE1UFljiDOEZoyaTRHhqdDfBd/s1clXHB7Qw8CZJUYYOpovHZihAbRvBNjxkReuJuhg==
NSEC 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. xzogVm6Lwe9hrGC2Wsl5uQZwcz4wZC3viqjJQU1J0GE53HuCTJqRN34wPZBP3Bm7zzSl31EVHRKI2iaC9+TpCw==

Question and response

Question

dig ns2.wntelecom.net.br. RRSIG

Answer

ns2.wntelecom.net.br. 3600 RRSIG A 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. LzbVj17btLrTnlEJHqYRax3J11mcPXk71j0A7k/1fJVyRZTV6FRtuV00wT3eV8V4YFZxkbjvynALtZ3QnFNvSw== ns2.wntelecom.net.br. 3600 RRSIG AAAA 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. sdeoa6uBqUVT9fHZo10rE1UFljiDOEZoyaTRHhqdDfBd/s1clXHB7Qw8CZJUYYOpovHZihAbRvBNjxkReuJuhg== ns2.wntelecom.net.br. 3600 RRSIG NSEC 13 4 3600 20260614040005 20260517040005 51247 wntelecom.net.br. xzogVm6Lwe9hrGC2Wsl5uQZwcz4wZC3viqjJQU1J0GE53HuCTJqRN34wPZBP3Bm7zzSl31EVHRKI2iaC9+TpCw==

Authority

The response has no authority records.

Additional

. 0 OPT ; payload 1232, xrcode 0, version 0, flags 0

About these results

This page shows the RRSIG records for ns2.wntelecom.net.br. RRSIG records contain the DNSSEC signatures for a set of DNS records. Resolvers verify them with DNSKEY records to confirm that the data is authentic and unchanged.

Find other DNS records for ns2.wntelecom.net.br:

A AAAA AFSDB APL AXFR CAA CDNSKEY CDS CERT CNAME CSYNC DHCID DLV DNAME DNSKEY DS EUI48 EUI64 HINFO HIP HTTPS IPSECKEY IXFR KEY KX LOC MX NAPTR NS NSEC3 NSEC3PARAM NSEC NXT OPENPGPKEY OPT PTR RP SIG SMIMEA SOA SPF SSHFP SVCB SRV TA TKEY TLSA TSIG TXT URI ZONEMD

The results on this page are freshly fetched just for you when you loaded this page. Wirewiki queried the authoritative DNS servers for ns2.wntelecom.net.br. That means that these results are guaranteed to be accurate, because there are no caches in between that could potentially cause staleness.

To look up RRSIG records for another hostname or domain name, go back to RRSIG lookup, or use DNS lookup to find all DNS records.