jinb.in 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=2a02:2268:ffff:ffff::4,Address Type=IPv6,Server=Apache,HTTP Status=404] vs [Address=178.128.197.13,Address Type=IPv4,Server=nginx/1.14.0 + Phusion Passenger 6.0.4,HTTP Status=404]
Requests made to the domain
Request to: jinb.in/2a02:2268:ffff:ffff::4, Result: [Address=2a02:2268:ffff:ffff::4,Address Type=IPv6,Server=Apache,HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://jinb.in/.well-known/acme-challenge/letsdebug-test (using initial IP 2a02:2268:ffff:ffff::4)
@0ms: Dialing 2a02:2268:ffff:ffff::4
@153ms: Server response: HTTP 404 Not Found
Request to: jinb.in/178.128.197.13, Result: [Address=178.128.197.13,Address Type=IPv4,Server=nginx/1.14.0 + Phusion Passenger 6.0.4,HTTP Status=404], Issue:
Trace:
@0ms: Making a request to http://jinb.in/.well-known/acme-challenge/letsdebug-test (using initial IP 178.128.197.13)
@0ms: Dialing 178.128.197.13
@1556ms: Server response: HTTP 404 Not Found
A and AAAA records found for this domain
jinb.in. 0 IN A 178.128.197.13
jinb.in. 0 IN AAAA 2a02:2268:ffff:ffff::4
Challenge update failures for jinb.in in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/82692651
acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from http://jinb.in/.well-known/acme-challenge/4rlPCb9CZyzxyOGAqnP1JnMukjARWBaCeUaO_E0R6Qg [2a02:2268:ffff:ffff::4]: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"
The IANA public suffix is the TLD of the Registered Domain
The TLD for jinb.in is: in
The current status.io status for Let's Encrypt
Operational