3.d-53.jp. RRSIG records

RRSIG
10m
SOA 13 3 600 20260715152015 20260614152015 6628 3.d-53.jp. cj+0YcIDv43m6zwhXNHmpMMbzWSx7iILNF/GYmqmMdvO34iuo2msYr2W01KsZ9CtXGmFJJLnXov4Vd2yuVgv5Q==
NS 13 3 600 20260715152015 20260614152015 6628 3.d-53.jp. 0nN5KOTJ1dOiG6M7YFR3TYLw8ljYyvNptnUfz8sjPxEh9RCPNgBVsLEOY9QnjDxxRVZi8GtWDuNa26krRWzqig==
DNSKEY 13 3 600 20260715152015 20260614152015 62618 3.d-53.jp. DwNIcZFnzAVck4vT2x6EIgmI6t7CCW768WNHqDMq4/zgCHCqUgmcib1mzOM7YEfEcTnwiOJNljsVmV25Mp91BA==
NSEC3PARAM 13 3 0 20260715152015 20260614152015 6628 3.d-53.jp. 6YoGFSmsu8Lfj0CSx2GlAMtZbeLai2aSZnP8Pfv+Flbszl13hI/C5IhV7XJWuTyPddGPxwhH2Ruox1wdHnXawQ==

Question and response

Question

dig 3.d-53.jp. RRSIG

Answer

3.d-53.jp. 600 RRSIG SOA 13 3 600 20260715152015 20260614152015 6628 3.d-53.jp. cj+0YcIDv43m6zwhXNHmpMMbzWSx7iILNF/GYmqmMdvO34iuo2msYr2W01KsZ9CtXGmFJJLnXov4Vd2yuVgv5Q== 3.d-53.jp. 600 RRSIG NS 13 3 600 20260715152015 20260614152015 6628 3.d-53.jp. 0nN5KOTJ1dOiG6M7YFR3TYLw8ljYyvNptnUfz8sjPxEh9RCPNgBVsLEOY9QnjDxxRVZi8GtWDuNa26krRWzqig== 3.d-53.jp. 600 RRSIG DNSKEY 13 3 600 20260715152015 20260614152015 62618 3.d-53.jp. DwNIcZFnzAVck4vT2x6EIgmI6t7CCW768WNHqDMq4/zgCHCqUgmcib1mzOM7YEfEcTnwiOJNljsVmV25Mp91BA== 3.d-53.jp. 0 RRSIG NSEC3PARAM 13 3 0 20260715152015 20260614152015 6628 3.d-53.jp. 6YoGFSmsu8Lfj0CSx2GlAMtZbeLai2aSZnP8Pfv+Flbszl13hI/C5IhV7XJWuTyPddGPxwhH2Ruox1wdHnXawQ==

Authority

3.d-53.jp. 600 NS ns.iij-dns.jp. 3.d-53.jp. 600 NS ns.iij-dns.biz. 3.d-53.jp. 600 NS ns.iij-dns.net.

Additional

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

About these results

This page shows the RRSIG records for 3.d-53.jp.. 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 3.d-53.jp.:

The results on this page are freshly fetched just for you when you loaded this page. Wirewiki queried the authoritative DNS servers for 3.d-53.jp.. 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.