dev.lubyc.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:4860:4802:36::15,Address Type=IPv6,Server=nginx,HTTP Status=403] vs [Address=34.66.232.202,Address Type=IPv4,Server=nginx,HTTP Status=404]
Requests made to the domain
Request to: dev.lubyc.com/2001:4860:4802:36::15, Result: [Address=2001:4860:4802:36::15,Address Type=IPv6,Server=nginx,HTTP Status=403], Issue:
Trace:
@0ms: Making a request to http://dev.lubyc.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:4860:4802:36::15)
@0ms: Dialing 2001:4860:4802:36::15
@140ms: Server response: HTTP 403 Forbidden
Request to: dev.lubyc.com/2001:4860:4802:34::15, Result: [Address=2001:4860:4802:34::15,Address Type=IPv6,Server=nginx,HTTP Status=403], Issue:
Trace:
@0ms: Making a request to http://dev.lubyc.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:4860:4802:34::15)
@0ms: Dialing 2001:4860:4802:34::15
@132ms: Server response: HTTP 403 Forbidden
Request to: dev.lubyc.com/2001:4860:4802:32::15, Result: [Address=2001:4860:4802:32::15,Address Type=IPv6,Server=nginx,HTTP Status=403], Issue:
Trace:
@0ms: Making a request to http://dev.lubyc.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:4860:4802:32::15)
@0ms: Dialing 2001:4860:4802:32::15
@166ms: Server response: HTTP 403 Forbidden
Request to: dev.lubyc.com/2001:4860:4802:38::15, Result: [Address=2001:4860:4802:38::15,Address Type=IPv6,Server=nginx,HTTP Status=403], Issue:
Trace:
@0ms: Making a request to http://dev.lubyc.com/.well-known/acme-challenge/letsdebug-test (using initial IP 2001:4860:4802:38::15)
@0ms: Dialing 2001:4860:4802:38::15
@137ms: Server response: HTTP 403 Forbidden
Request to: dev.lubyc.com/34.66.232.202, Result: [Address=34.66.232.202,Address Type=IPv4,Server=nginx,HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://dev.lubyc.com/.well-known/acme-challenge/letsdebug-test (using initial IP 34.66.232.202)
@0ms: Dialing 34.66.232.202
@60ms: Server response: HTTP 404 Not Found
A and AAAA records found for this domain
dev.lubyc.com. 0 IN A 34.66.232.202
dev.lubyc.com. 0 IN AAAA 2001:4860:4802:36::15
dev.lubyc.com. 0 IN AAAA 2001:4860:4802:34::15
dev.lubyc.com. 0 IN AAAA 2001:4860:4802:32::15
dev.lubyc.com. 0 IN AAAA 2001:4860:4802:38::15
Challenge update failures for dev.lubyc.com in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/48002932
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://dev.lubyc.com/.well-known/acme-challenge/I77KaOz2iDx1kv7sWPj-06WzI8qEYKi-Bz4uhP3ar_o [2001:4860:4802:36::15]: "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>403 Forbidden</h1></center>\r\n<hr><center>"
The IANA public suffix is the TLD of the Registered Domain
The TLD for dev.lubyc.com is: com
2 Certificates contributing to rate limits for this domain
Serial: 304545614202542413732850991681027290250994
NotBefore: 2019-08-27 19:02:59 +0000 UTC
Names: [dev.lubyc.com]
Serial: 309546267265622932793544210671838376918964
NotBefore: 2019-08-26 15:09:09 +0000 UTC
Names: [lubyc.com]
The current status.io status for Let's Encrypt
Operational