| 1. General Results, most used to calculate the result |
| A | name "survey.epam.com" is subdomain, 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: survey.epam.com has 4 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: survey.epam.com has 2 ipv4, 2 ipv6 addresses
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| 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.
|
| 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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (8 urls)
|
| https://survey.epam.com/ 104.18.12.91
|
| Url with incomplete Content-Type - header - missing charset
|
| https://survey.epam.com/ 104.18.13.91
|
| Url with incomplete Content-Type - header - missing charset
|
| https://survey.epam.com/ 2606:4700::6812:c5b
|
| Url with incomplete Content-Type - header - missing charset
|
| https://survey.epam.com/ 2606:4700::6812:d5b
|
| Url with incomplete Content-Type - header - missing charset
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.12.91
|
| Url with incomplete Content-Type - header - missing charset
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.13.91
|
| Url with incomplete Content-Type - header - missing charset
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:c5b
|
| Url with incomplete Content-Type - header - missing charset
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:d5b
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://survey.epam.com/ 104.18.12.91
| https://survey.epam.com/
| Correct redirect http - https with the same domain name
|
| A | http://survey.epam.com/ 104.18.13.91
| https://survey.epam.com/
| Correct redirect http - https with the same domain name
|
| A | http://survey.epam.com/ 2606:4700::6812:c5b
| https://survey.epam.com/
| Correct redirect http - https with the same domain name
|
| A | http://survey.epam.com/ 2606:4700::6812:d5b
| https://survey.epam.com/
| Correct redirect http - https with the same domain name
|
| P | https://104.18.12.91/ 104.18.12.91
|
| Error creating a TLS-Connection: No more details available.
|
| P | https://104.18.13.91/ 104.18.13.91
|
| Error creating a TLS-Connection: No more details available.
|
| P | https://[2606:4700:0000:0000:0000:0000:6812:0c5b]/ 2606:4700::6812:c5b
|
| Error creating a TLS-Connection: No more details available.
|
| P | https://[2606:4700:0000:0000:0000:0000:6812:0d5b]/ 2606:4700::6812:d5b
|
| Error creating a TLS-Connection: No more details available.
|
| 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 survey.epam.com, 4 ip addresses.
|
| 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 survey.epam.com, 4 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.survey.epam.com
|
| 2. Header-Checks |
| A | survey.epam.com 104.18.12.91
| Content-Security-Policy
| Ok: Header without syntax errors found: style-src https://*.epam.com 'unsafe-inline' 'self'; img-src https: //*.epam.com data: 'self'; object-src 'none';: default-src https: //*.epam.com 'self';
|
| F |
|
| Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| E |
|
| Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| A | survey.epam.com 104.18.13.91
| Content-Security-Policy
| Ok: Header without syntax errors found: style-src https://*.epam.com 'unsafe-inline' 'self'; img-src https: //*.epam.com data: 'self'; object-src 'none';: default-src https: //*.epam.com 'self';
|
| F |
|
| Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| E |
|
| Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| A | survey.epam.com 2606:4700::6812:c5b
| Content-Security-Policy
| Ok: Header without syntax errors found: style-src https://*.epam.com 'unsafe-inline' 'self'; img-src https: //*.epam.com data: 'self'; object-src 'none';: default-src https: //*.epam.com 'self';
|
| F |
|
| Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| E |
|
| Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| A | survey.epam.com 2606:4700::6812:d5b
| Content-Security-Policy
| Ok: Header without syntax errors found: style-src https://*.epam.com 'unsafe-inline' 'self'; img-src https: //*.epam.com data: 'self'; object-src 'none';: default-src https: //*.epam.com 'self';
|
| F |
|
| Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition.
|
| A |
|
| Good: default-src without 'unsafe-inline' or 'unsave-eval'.
|
| E |
|
| Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No frame-ancestors directive found. Use one to limit the pages allowed to use this page in frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
|
| E |
|
| Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
|
| A |
|
| Good: object-src only with 'none' or 'self' found, no scheme, no other urls. That blocks object / embed / applet - elements.
|
| E |
|
| Critical: No script-src defined, the default-src used as fallback allows too much. script-src should always restricted.
|
| A |
|
| Good: frame-src without data: defined or frame-src missing and the default-src used as fallback not allows the data: schema. That blocks hidden code injection. Insert <iframe src="data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw+PGh0bWw+PGJvZHk+PHA+YmVmb3JlPHNjcmlwdCB0eXBlPSJ0ZXh0L2phdmFzY3JpcHQiPmFsZXJ0KCdYU1MnKTwvc2NyaXB0PjxwPmFmdGVyPC9ib2R5PjwvaHRtbD4="></iframe> in your page and see what happens.
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: SAMEORIGIN
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. SAMEORIGIN. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
|
| A |
| X-Xss-Protection
| Ok: Header without syntax errors found: 1; mode=block
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
|
| F | survey.epam.com 104.18.12.91
| Referrer-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 104.18.12.91
| Permissions-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 104.18.13.91
| Referrer-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 104.18.13.91
| Permissions-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 2606:4700::6812:c5b
| Referrer-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 2606:4700::6812:c5b
| Permissions-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 2606:4700::6812:d5b
| Referrer-Policy
| Critical: Missing Header:
|
| F | survey.epam.com 2606:4700::6812:d5b
| Permissions-Policy
| Critical: Missing Header:
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 23 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
|
| A | Info:: 23 Queries complete, 23 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.8 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 6 different Name Servers found: a10-64.akam.net, a11-65.akam.net, a1-195.akam.net, a14-66.akam.net, a20-67.akam.net, a7-64.akam.net, 6 Name Servers included in Delegation: a1-195.akam.net, a10-64.akam.net, a11-65.akam.net, a14-66.akam.net, a20-67.akam.net, a7-64.akam.net, 6 Name Servers included in 1 Zone definitions: a1-195.akam.net, a10-64.akam.net, a11-65.akam.net, a14-66.akam.net, a20-67.akam.net, a7-64.akam.net, 1 Name Servers listed in SOA.Primary: a1-195.akam.net.
|
| A | Good: Only one SOA.Primary Name Server found.: a1-195.akam.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a1-195.akam.net.
|
| 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 | Info: Ipv4-Subnet-list: 6 Name Servers, 6 different subnets (first Byte): 184., 193., 23., 84., 95., 96., 6 different subnets (first two Bytes): 184.26., 193.108., 23.61., 84.53., 95.100., 96.7., 6 different subnets (first three Bytes): 184.26.161., 193.108.91., 23.61.199., 84.53.139., 95.100.175., 96.7.50.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 2 different subnets (first block): 2600:, 2a02:, 4 different subnets (first two blocks): 2600:1401:, 2600:1406:, 2600:1480:, 2a02:26f0:, 6 different subnets (first three blocks): 2600:1401:0002:, 2600:1406:0032:, 2600:1480:0001:, 2600:1480:1800:, 2600:1480:d000:, 2a02:26f0:0067:, 6 different subnets (first four blocks): 2600:1401:0002:0000:, 2600:1406:0032:0000:, 2600:1480:0001:0000:, 2600:1480:1800:0000:, 2600:1480:d000:0000:, 2a02:26f0:0067:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 12 good Nameserver
|
| X | Nameserver Timeout checking Echo Capitalization: a10-64.akam.net / 96.7.50.64
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: a1-195.akam.net: 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: a14-66.akam.net / 184.26.161.66: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
|
| 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://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.12.91
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.13.91
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:c5b
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:d5b
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| https://survey.epam.com/ 104.18.12.91
|
| 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://survey.epam.com/ 104.18.13.91
|
| 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://survey.epam.com/ 2606:4700::6812:c5b
|
| 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://survey.epam.com/ 2606:4700::6812:d5b
|
| 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.
|
| A | Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
|
| A | Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
|
| A | Good: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
|
| https://survey.epam.com/ 104.18.12.91
|
| 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.: 1 script elements without defer/async.
|
| https://survey.epam.com/ 104.18.13.91
|
| 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.: 1 script elements without defer/async.
|
| https://survey.epam.com/ 2606:4700::6812:c5b
|
| 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.: 1 script elements without defer/async.
|
| https://survey.epam.com/ 2606:4700::6812:d5b
|
| 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.: 1 script elements without defer/async.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.12.91
|
| 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.: 1 script elements without defer/async.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.18.13.91
|
| 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.: 1 script elements without defer/async.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:c5b
|
| 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.: 1 script elements without defer/async.
|
| http://survey.epam.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2606:4700::6812:d5b
|
| 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.: 1 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. 40 external CSS / JavaScript files found
|
| 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, 40 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 40 complete.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| 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: 264544 milliseconds, 264.544 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)