1. General Results, most used to calculate the result A name "dev.pdam.co.id" is subdomain, public suffix is ".co.id", top-level-domain is ".id", top-level-domain-type is "country-code", Country is Indonesia, tld-manager is "Perkumpulan Pengelola Nama Domain Internet Indonesia (PANDI)", num .id-domains preloaded: 511 (complete: 221801) A Good: All ip addresses are public addresses Warning: Only one ip address found: dev.pdam.co.id has only one ip address. Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: dev.pdam.co.id has no ipv6 address. A Good: No asked Authoritative Name Server had a timeout A DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain dev.pdam.co.id, 1 ip addresses. B No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.dev.pdam.co.id 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) U No https result with http status 2** or 4** (standard-check) found, no header checked. 3. DNS- and NameServer - Checks A Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers. A Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers. A Info:: 2 different Name Servers found: ns3.niagahoster.com, ns4.niagahoster.com, 2 Name Servers included in Delegation: ns3.niagahoster.com, ns4.niagahoster.com, 2 Name Servers included in 1 Zone definitions: ns3.niagahoster.com, ns4.niagahoster.com, 1 Name Servers listed in SOA.Primary: ns3.niagahoster.com. A Good: Only one SOA.Primary Name Server found.: ns3.niagahoster.com. A Good: SOA.Primary Name Server included in the delegation set.: ns3.niagahoster.com. A Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns3.niagahoster.com, ns4.niagahoster.com A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: niagahoster.com A Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: ID, SG A Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 153., 45., 2 different subnets (first two Bytes): 153.92., 45.90., 2 different subnets (first three Bytes): 153.92.15., 45.90.230. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Good: Nameserver supports TCP connections: 1 good Nameserver A Good: Nameserver supports Echo Capitalization: 1 good Nameserver X Nameserver Timeout checking Echo Capitalization: d.dns.id / 45.126.57.57 X Nameserver Timeout checking Echo Capitalization: e.dns.id X Nameserver Timeout checking Echo Capitalization: e.dns.id / 103.19.177.177 A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver X Nameserver Timeout checking EDNS512: d.dns.id X Nameserver Timeout checking EDNS512: e.dns.id / 103.19.177.177 X Nameserver Timeout checking EDNS512: e.dns.id / 2001:df5:4000:4::4 A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver Nameserver doesn't pass all EDNS-Checks: d.dns.id: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: d.dns.id / 45.126.57.57: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: d.dns.id / 2402:ee80:d::d: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: e.dns.id: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: e.dns.id / 103.19.177.177: OP100: fatal timeout. FLAGS: fatal timeout. V1: ok. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: e.dns.id / 2001:df5:4000:4::4: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns3.niagahoster.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. A Good: All SOA have the same Serial Number Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks http://dev.pdam.co.id/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.175.217.174 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Info: No img element found, no alt attribute checked A Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx A Duration: 467063 milliseconds, 467.063 seconds