ljm.name has both AAAA (IPv6) and A (IPv4) records. While they both 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 the IPv4 and IPv6 addresses may unintentionally point to different servers, which would cause validation to fail.
[Address Type=IPv4,Server=Apache/2.2.22 (Debian),HTTP Status=404] vs [Address Type=IPv6,Server=Apache/2.4.10,HTTP Status=200]
Requests made to the domain
Request to: ljm.name/2a00:4e40:1:1::2:202, Result: [Address Type=IPv6,Server=Apache/2.4.10,HTTP Status=200], Issue:
Trace:
@0ms: Making a request to http://ljm.name/.well-known/acme-challenge/letsdebug-test (using initial IP 2a00:4e40:1:1::2:202)
@0ms: Dialing 2a00:4e40:1:1::2:202
@153ms: Server response: HTTP 200 OK
Request to: ljm.name/83.163.211.192, Result: [Address Type=IPv4,Server=Apache/2.2.22 (Debian),HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://ljm.name/.well-known/acme-challenge/letsdebug-test (using initial IP 83.163.211.192)
@0ms: Dialing 83.163.211.192
@214ms: Server response: HTTP 404 Not Found
A and AAAA records found for this domain
ljm.name. 0 IN A 83.163.211.192
ljm.name. 0 IN AAAA 2a00:4e40:1:1::2:202
Challenge update failures for ljm.name in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/9651287
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://ljm.name/.well-known/acme-challenge/N17PDVh6MymGkU7boBMZQkCm4-JtZVp0RqTfHRFBjwY: "<!doctype html><html lang=\"nl\"><head> <meta charset=\"UTF-8\"> <meta name=\"viewport\" content=\"width=device-width, user-scalable=no"
The IANA public suffix is the TLD of the Registered Domain
The TLD for ljm.name is: name
The current status.io status for Let's Encrypt
Operational