All changes pushed to this repository are automatically deployed to nameservers every 10th minute. Syntax is checked for changes go live however so please be aware when pushing changes.
From September 2017, CAA records will be mandatory for CAs. A CAA record is a DNS record which allows DNS admins to authorise CAs to issue SSL certificates for certain domains. This decreases the chance of phising through fake issuance of SSL certificates from genuine CAs. Further, this allows Miraheze to more realistically control which CAs are allowed onto our platform.
Unfortunately due to a lack of upstream implementation, CAA records have to defined using TYPE257 instead of the more appealing CAA.
To allow a CA to issue a certificate, add the follow line below the relevant CA to the DNS records.
Comodo: TYPE257 # 19 00056973737565636F6D6F646F63612E636F6D
Let's Encrypt: TYPE257 # 22 000569737375656C657473656E63727970742E6F7267
Symantec: TYPE257 # 19 0005697373756573796D616E7465632E636F6D
All CAA definitions should end with a location to email violations too which can be done as: TYPE257 # 37 0005696F6465666D61696C746F3A6F7065726174696F6E73406D69726168657A652E6F7267
No all CAs currently support CAA such as GlobalSign and GoDaddy. This has to change in the next month however.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent