| 1. General Results, most used to calculate the result |
| A | name "merchant.priceblaze.pk" is subdomain, public suffix is "pk", top-level-domain-type is "country-code", Country is Pakistan, tld-manager is "PKNIC"
|
| A | Good: All ip addresses are public addresses
|
| 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
|
| A | Good: destination is https
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://merchant.priceblaze.pk
|
| Missing HSTS-Header
|
| B | https://merchant.priceblaze.pk/ 38.108.7.164
|
| Missing HSTS-Header
|
| B | https://merchant.priceblaze.pk
| csrftoken=pqsucHsChXXzAt6jEGM9AziXlZznLCUs; Path=/; Domain=merchant.priceblaze.pk; Expires=2020-03-25 11:49:04
| Cookie sent via https, but not marked as secure
|
| B | https://merchant.priceblaze.pk/ 38.108.7.164
| csrftoken=FbbqUESEFpxpmYu7tAc10UGG8sPI21jb; Path=/; Domain=merchant.priceblaze.pk; Expires=2020-03-25 11:49:02
| Cookie sent via https, but not marked as secure
|
| C | Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
|
| I | https://merchant.priceblaze.pk/ 38.108.7.164
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| I | https://merchant.priceblaze.pk
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| 3. DNS- and NameServer - Checks |
| A | Good: Nameserver supports TCP connections: 1 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 1 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
|
| 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: ns3.weatherlycloud.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 |
| Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| 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: 43627 milliseconds, 43.627 seconds
|