| 1. General Results, most used to calculate the result |
A | name "live.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 86299 (complete: 221801)
|
A | Good: All ip addresses are public addresses
|
A | Good: Minimal 2 ip addresses per domain name found: live.com has 2 different ip addresses (authoritative).
|
A | Good: Minimal 2 ip addresses per domain name found: www.live.com has 2 different ip addresses (authoritative).
|
A | Good: Ipv4 and Ipv6 addresses per domain name found: www.live.com has 1 ipv4, 1 ipv6 addresses
|
| 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: live.com has no ipv6 address.
|
A | Good: No asked Authoritative Name Server had a timeout
|
A | https://live.com/ 204.79.197.212
| https://outlook.live.com/owa/
| Correct redirect https to https
|
A | Good: destination is https
|
A | Good - only one version with Http-Status 200
|
A | Good: one preferred version: non-www is preferred
|
A | Good: No cookie sent via http.
|
A | Good: every cookie sent via https is marked as secure
|
| Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
|
| HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
|
A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
B | https://live.com/ 204.79.197.212
|
| Missing HSTS-Header
|
B | https://www.live.com/ 204.79.197.212
|
| Missing HSTS-Header
|
B | https://www.live.com/ 2620:1ec:c11::212
|
| Missing HSTS-Header
|
B | https://outlook.live.com/owa/
| RoutingKeyCookie=; expires=Wed, 26-May-1993 04:09:03 GMT; path=/; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
B | https://outlook.live.com/owa/
| HostSwitchPrg=; expires=Wed, 26-May-1993 04:09:03 GMT; path=/; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
B | https://outlook.live.com/owa/
| OptInPrg=; expires=Wed, 26-May-1993 04:09:03 GMT; path=/; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
B | https://outlook.live.com/owa/
| logonLatency=LGN01=638206709430607413; domain=live.com; path=/; secure; HttpOnly
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
B | https://outlook.live.com/owa/
| O365Consumer=; expires=Wed, 26-May-1993 04:09:03 GMT; path=/; secure
| Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
|
E | http://live.com/ 204.79.197.212
| https://outlook.live.com/owa/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
E | http://www.live.com/ 204.79.197.212
| https://outlook.live.com/owa/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
E | http://www.live.com/ 2620:1ec:c11::212
| https://outlook.live.com/owa/
| Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
M | https://204.79.197.212/ 204.79.197.212
|
| Misconfiguration - main pages should never send http status 400 - 499
|
M | https://[2620:01ec:0c11:0000:0000:0000:0000:0212]/ 2620:1ec:c11::212
|
| Misconfiguration - main pages should never send http status 400 - 499
|
N | https://204.79.197.212/ 204.79.197.212
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
N | https://[2620:01ec:0c11:0000:0000:0000:0000:0212]/ 2620:1ec:c11::212
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
X | Fatal error: Nameserver doesn't support TCP connection: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 40.66.196.211: Timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 2603:10b6:628:2::19: Timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 40.66.197.21: Timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 2603:10b6:500::21: Timeout
|
A | Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.live.com, 2 ip addresses.
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain live.com, 1 ip addresses, 1 different http results.
|
| Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.live.com, 2 ip addresses, 1 different http results.
|
A | Good: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.live.com
|
A | Good: _mta-sts TXT record is valid.
|
B | Bad: Valid _mta-sts TXT found, but no ip address of the subdomain mta-sts found _mta-sts.live.com
|
| 2. Header-Checks |
A | outlook.live.com
| report-to
| Ok: Header without syntax errors found: {"group":"NelOfficeUpload1","max_age":7200,"endpoints":[{"url":"https://exo.nel.measure.office.net/api/report?TenantId=&FrontEnd=Cafe&DestinationEndpoint=HHN"}],"include_subdomains":true}
|
A |
|
| Ok: Header without syntax errors found: {"group":"NelOfficeUpload1","max_age":7200,"endpoints":[{"url":"https://exo.nel.measure.office.net/api/report?TenantId=&FrontEnd=Cafe&DestinationEndpoint=HHN"}],"include_subdomains":true}
|
A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
F | outlook.live.com
| Content-Security-Policy
| Critical: Missing Header:
|
F | outlook.live.com
| Referrer-Policy
| Critical: Missing Header:
|
F | outlook.live.com
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
A | Info:: 34 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 10 Name Servers.
|
A | Info:: 34 Queries complete, 34 with IPv6, 0 with IPv4.
|
A | Good: All DNS Queries done via IPv6.
|
A | Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.nse12.o365filtering.com (104.47.38.8), nse13.o365filtering.com (104.47.2.8), nse21.o365filtering.com (104.47.40.8)
|
| Ok (4 - 8):: An average of 3.4 queries per domain name server required to find all ip addresses of all name servers.
|
A | Info:: 10 different Name Servers found: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com, ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns5-34.azure-dns.com, ns7-34.azure-dns.org, ns8-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com, 8 Name Servers included in Delegation: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns5-34.azure-dns.com, ns7-34.azure-dns.org, ns8-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, 8 Name Servers included in 2 Zone definitions: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns5-34.azure-dns.com, ns7-34.azure-dns.org, ns8-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, 2 Name Servers listed in SOA.Primary: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com, ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com.
|
| Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com,ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com,ph0mgt0101dc003.prdmgt01.prod.exchangelabs.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: 10 different Name Servers found
|
A | Good: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (6 Name Servers without IPv6)
|
A | Good: Name servers with different Top Level Domains / Public Suffix List entries found: 10 Name Servers, 4 Top Level Domains: com, org, net, info
|
A | Good: Name Servers with different domain names found.: 6 different Domains found
|
A | Good: Name servers with different Country locations found: 10 Name Servers, 4 Countries: CA, IE, SE, US
|
A | Info: Ipv4-Subnet-list: 10 Name Servers, 4 different subnets (first Byte): 104., 13., 150., 40., 4 different subnets (first two Bytes): 104.47., 13.107., 150.171., 40.66., 10 different subnets (first three Bytes): 104.47.2., 104.47.38., 104.47.40., 13.107.207., 13.107.223., 150.171.10., 150.171.11., 150.171.16., 40.66.196., 40.66.197.
|
A | Good: Name Server IPv4-addresses from different subnet found:
|
A | Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2603:, 2620:, 3 different subnets (first two blocks): 2603:1061:, 2603:10b6:, 2620:01ec:, 4 different subnets (first three blocks): 2603:1061:0000:, 2603:10b6:0500:, 2603:10b6:0628:, 2620:01ec:08ec:, 4 different subnets (first four blocks): 2603:1061:0000:0010:, 2603:10b6:0500:0000:, 2603:10b6:0628:0002:, 2620:01ec:08ec:0010:
|
A | Good: Name Server IPv6 addresses from different subnets found.
|
A | Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
|
X | Nameserver Timeout checking Echo Capitalization: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 40.66.196.211
|
X | Nameserver Timeout checking Echo Capitalization: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 2603:10b6:628:2::19
|
X | Nameserver Timeout checking Echo Capitalization: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 40.66.197.21
|
X | Nameserver Timeout checking Echo Capitalization: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 2603:10b6:500::21
|
X | Nameserver Timeout checking EDNS512: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 40.66.196.211
|
X | Nameserver Timeout checking EDNS512: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 2603:10b6:628:2::19
|
X | Nameserver Timeout checking EDNS512: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 40.66.197.21
|
X | Nameserver Timeout checking EDNS512: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 2603:10b6:500::21
|
| Nameserver doesn't pass all EDNS-Checks: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.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.
|
| Nameserver doesn't pass all EDNS-Checks: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 40.66.196.211: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. 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: ch0mgt0101dc001.prdmgt01.prod.exchangelabs.com / 2603:10b6:628:2::19: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. 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: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.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.
|
| Nameserver doesn't pass all EDNS-Checks: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 40.66.197.21: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. 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: ph0mgt0101dc003.prdmgt01.prod.exchangelabs.com / 2603:10b6:500::21: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
X | Fatal error: Nameservers with different SOA Serial Numbers
|
A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: dtrust.de is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: entrust.net is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: microsoft.com is allowed to create certificates
|
| Warning: Unknown CAA found: microsoft.com isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://outlook.live.com/owa/
|
| Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
|
| https://outlook.live.com/owa/
|
| Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
|
A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| https://outlook.live.com/owa/
|
| Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 7 script elements without defer/async.
|
A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 8 external CSS / JavaScript files found
|
A | Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 6 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
|
| Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 7 with Cache-Control long enough, 8 complete.
|
A | Good: All images are sent with a long Cache-Control header (minimum 7 days). So the browser can reuse these files, no download is required. 6 image files with long Cache-Control max-age found
|
A | Good: Some checked attribute values are enclosed in quotation marks (" or ').: 70 Html-Elements checked, 55 without problems.
|
I | Wrong: Attribute values found, not enclosed in quotation marks (" or ').: 15 Html-Elements with attributes and missing enclosed quotation marks found. 18 wrong attributes.
|
A | Good: Some img-elements have a valid alt-attribute.: 7 img-elements found, 1 img-elements with correct alt-attributes (defined, not an empty value).
|
| Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 6 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
|
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: 379584 milliseconds, 379.584 seconds
|