f.d-53.jp RRSIG records

RRSIG
0s
NSEC3PARAM 13 3 0 20260630151042 20260530151042 51179 f.d-53.jp. b3pIdid28VpkL3xhlPYbHW/OvFkEnHSAKRDlD3UWh4B7bUyiGaoWcCQJ6dsRpo2tDAdK/Xep3nVbmgBzukwxWQ==
SOA 13 3 600 20260630151042 20260530151042 51179 f.d-53.jp. iLGt+wIGI/1Uh9vBaPSswvschSzkQtXbGI8x73nGW637Q+74VGH0KZlqoELylf6rcryWDa5iYkgsO52PKCghOg==
NS 13 3 600 20260630151042 20260530151042 51179 f.d-53.jp. yp9sbUugOFjA1fX/FHCVvDuhkqBLtMQbNWTb1XMSFoSLcqAGQ9Lz5O6oyJdZu7a63lpAvPZ1Sj19aGij/GFwBQ==
DNSKEY 13 3 600 20260630151042 20260530151042 58272 f.d-53.jp. mDoLp3wbuMwdJUiThtZdQXmRRpXu0r8W6GVjj0qzi3g7uuSK5oQZiB1BdrcRKZBXWo9Hyxnhi2a4EreR1aMuVQ==

Question and response

Question

dig f.d-53.jp. RRSIG

Answer

f.d-53.jp. 0 RRSIG NSEC3PARAM 13 3 0 20260630151042 20260530151042 51179 f.d-53.jp. b3pIdid28VpkL3xhlPYbHW/OvFkEnHSAKRDlD3UWh4B7bUyiGaoWcCQJ6dsRpo2tDAdK/Xep3nVbmgBzukwxWQ== f.d-53.jp. 600 RRSIG SOA 13 3 600 20260630151042 20260530151042 51179 f.d-53.jp. iLGt+wIGI/1Uh9vBaPSswvschSzkQtXbGI8x73nGW637Q+74VGH0KZlqoELylf6rcryWDa5iYkgsO52PKCghOg== f.d-53.jp. 600 RRSIG NS 13 3 600 20260630151042 20260530151042 51179 f.d-53.jp. yp9sbUugOFjA1fX/FHCVvDuhkqBLtMQbNWTb1XMSFoSLcqAGQ9Lz5O6oyJdZu7a63lpAvPZ1Sj19aGij/GFwBQ== f.d-53.jp. 600 RRSIG DNSKEY 13 3 600 20260630151042 20260530151042 58272 f.d-53.jp. mDoLp3wbuMwdJUiThtZdQXmRRpXu0r8W6GVjj0qzi3g7uuSK5oQZiB1BdrcRKZBXWo9Hyxnhi2a4EreR1aMuVQ==

Authority

f.d-53.jp. 600 NS ns.iij-dns.jp. f.d-53.jp. 600 NS ns.iij-dns.biz. f.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 f.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 f.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 f.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.