github.com CAA records

CAA
1h
0 issue "digicert.com"
0 issue "globalsign.com"
0 issue "letsencrypt.org"
0 issue "sectigo.com"
0 issuewild "digicert.com"
0 issuewild "letsencrypt.org"
0 issuewild "sectigo.com"

Question and response

Question

dig github.com. CAA

Answer

github.com. 3600 CAA 0 issue "digicert.com" github.com. 3600 CAA 0 issue "globalsign.com" github.com. 3600 CAA 0 issue "letsencrypt.org" github.com. 3600 CAA 0 issue "sectigo.com" github.com. 3600 CAA 0 issuewild "digicert.com" github.com. 3600 CAA 0 issuewild "letsencrypt.org" github.com. 3600 CAA 0 issuewild "sectigo.com"

Authority

github.com. 900 NS dns1.p08.nsone.net. github.com. 900 NS dns2.p08.nsone.net. github.com. 900 NS dns3.p08.nsone.net. github.com. 900 NS dns4.p08.nsone.net. github.com. 900 NS ns-1283.awsdns-32.org. github.com. 900 NS ns-1707.awsdns-21.co.uk. github.com. 900 NS ns-421.awsdns-52.com. github.com. 900 NS ns-520.awsdns-01.net.

Additional

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

About these results

This page shows the CAA records for github.com. 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 github.com:

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