Let's Debug

Test result for gigantic.io using http-01

A fatal issue occured during the DNS lookup process for gigantic.io/CAA.
DNS response for gigantic.io/CAA did not have an acceptable response code: SERVFAIL
A fatal issue occured during the DNS lookup process for gigantic.io/A.
DNS response for gigantic.io/A did not have an acceptable response code: SERVFAIL
A fatal issue occured during the DNS lookup process for gigantic.io/AAAA.
DNS response for gigantic.io/AAAA did not have an acceptable response code: SERVFAIL
Fatal
No valid A or AAAA records could be ultimately resolved for gigantic.io. This means that Let's Encrypt would not be able to to connect to your domain to perform HTTP validation, since it would not know where to connect to.
No A or AAAA records found.
Error
gigantic.io is currently affected by Let's Encrypt-based rate limits (https://letsencrypt.org/docs/rate-limits/). You may review certificates that have already been issued by visiting https://crt.sh/?q=%gigantic.io . Please note that it is not possible to ask for a rate limit to be manually cleared.
The 'Certificates per Registered Domain' limit (20 certificates per week that share the same Registered Domain: gigantic.io) has been exceeded. There is no way to work around this rate limit. The next non-renewal certificate for this Registered Domain should be issuable after 2018-05-19 18:59:53 +0000 UTC (36h43m0s from now).

Submitted May 18 06:16:09 2018. Sat in queue for 4ms. Completed in 34s. Show verbose information.