jpberlin.de. CAA records

CAA
5m
0 issue "digicert.com"
0 iodef "mailto:[email protected]"
0 issue "letsencrypt.org"
0 iodef "mailto:[email protected]"

Question and response

Question

dig jpberlin.de. CAA

Answer

jpberlin.de. 300 CAA 0 issue "digicert.com" jpberlin.de. 300 CAA 0 iodef "mailto:[email protected]" jpberlin.de. 300 CAA 0 issue "letsencrypt.org" jpberlin.de. 300 CAA 0 iodef "mailto:[email protected]"

Authority

jpberlin.de. 300 NS dns4.cloudns.net. jpberlin.de. 300 NS dns7.cloudns.net. jpberlin.de. 300 NS ns2.jpberlin.de. jpberlin.de. 300 NS ns.jpberlin.de. jpberlin.de. 300 NS ns3.jpberlin.de.

Additional

ns.jpberlin.de. 300 A 91.198.250.3 ns2.jpberlin.de. 3600 A 194.150.191.56 ns3.jpberlin.de. 3600 A 88.198.52.15 ns.jpberlin.de. 1800 AAAA 2001:67c:2050:1:0:0:53:1 ns3.jpberlin.de. 300 AAAA 2a01:4f8:221:4381:0:0:0:1 . 0 OPT ; payload 4096, xrcode 0, version 0, flags 0

About these results

This page shows the CAA records for jpberlin.de.. CAA records tell certificate authorities which issuers are allowed to create TLS certificates for a domain. They are commonly used to reduce mis-issuance risk and enforce certificate issuance policy.

Find other DNS records for jpberlin.de.:

The results on this page are freshly fetched just for you when you loaded this page. Wirewiki queried the authoritative DNS servers for jpberlin.de.. 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 CAA records for another hostname or domain name, go back to CAA lookup, or use DNS lookup to find all DNS records.