Let's Debug

Test result for ammoairsoft.com using http-01

ammoairsoft.com has multiple IP addresses in its DNS records. While they appear to be accessible on the network, we have detected that they produce differing results when sent an ACME HTTP validation request. This may indicate that some of the IP addresses may unintentionally point to different servers, which would cause validation to fail.
[Address=2001:8d8:100f:f000::283,Address Type=IPv6,Server=nginx/1.10.3,HTTP Status=204] vs [Address=35.186.236.251,Address Type=IPv4,Server=,HTTP Status=200]
Debug
Requests made to the domain
Request to: ammoairsoft.com/2001:8d8:100f:f000::283, Result: [Address=2001:8d8:100f:f000::283,Address Type=IPv6,Server=nginx/1.10.3,HTTP Status=204], Issue:
Trace:
@0ms: Making a request to http://ammoairsoft.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:8d8:100f:f000::283)
@0ms: Dialing 2001:8d8:100f:f000::283
@189ms: Server response: HTTP 204

Request to: ammoairsoft.com/35.186.236.251, Result: [Address=35.186.236.251,Address Type=IPv4,Server=,HTTP Status=200], Issue:
Trace:
@0ms: Making a request to http://ammoairsoft.com/.well-known/acme-challenge/letsdebug-test (using initial IP 35.186.236.251)
@0ms: Dialing 35.186.236.251
@195ms: Server response: HTTP 200 OK

Debug
A and AAAA records found for this domain
ammoairsoft.com. 0 IN A 35.186.236.251
ammoairsoft.com. 0 IN AAAA 2001:8d8:100f:f000::283
An internal error occurred while checking the domain
Failed to query certwatch database to check rate limits: pq: unnamed prepared statement does not exist
Challenge update failures for ammoairsoft.com in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/73911469
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://ammoairsoft.com/.well-known/acme-challenge/1ay6i8eq0KYAgnFu5CZhrkGtECeJEUUDXMXZlmMgnrs [2001:8d8:100f:f000::283]: 204
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for ammoairsoft.com is: com
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Feb 4 13:54:16 2020. Sat in queue for 2ms. Completed in 2s. Hide verbose information.