| 1. General Results, most used to calculate the result |
| A | name "surfskip.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: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: surfskip.com has 8 different ip addresses (authoritative).
|
| A | Good: Minimal 2 ip addresses per domain name found: www.surfskip.com has 8 different ip addresses (authoritative).
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2a01:4f8:1c1e:d6f1::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2a01:4ff:f0:5f41::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| Correct redirect https to https
|
| A | https://surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.
|
| 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://surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2a01:4f8:1c1e:d6f1::1
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2a01:4ff:f0:5f41::1
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
|
| Missing HSTS-Header
|
| B | https://surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 5.161.47.86
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 76.223.91.20
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 195.201.128.179
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2a01:4f8:1c1e:d6f1::1
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2a01:4ff:f0:5f41::1
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2a01:4ff:1f0:dd50::1
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
|
| Missing HSTS-Header
|
| B | https://www.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
|
| Missing HSTS-Header
|
| E | http://surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2a01:4f8:1c1e:d6f1::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2a01:4ff:f0:5f41::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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://surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 5.161.47.86
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 76.223.91.20
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 195.201.128.179
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2a01:4f8:1c1e:d6f1::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2a01:4ff:f0:5f41::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2a01:4ff:1f0:dd50::1
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
| https://expireddomains.com/domain/surfskip.com?utm_source=redi
| 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.
|
| I | https://expireddomains.com/domain/surfskip.com?utm_source=redi
|
| Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
|
| K | http://surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| http://surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| http://surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| http://surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 195.201.128.179, Status 301
| http://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 5.161.230.87, Status -14
| http://www.surfskip.com/ 5.161.47.86, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 5.161.47.86, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 195.201.128.179, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 5.78.156.59, Status -14
| http://www.surfskip.com/ 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/ 5.161.230.87, Status -14
| http://www.surfskip.com/ 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| https://surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| https://surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://surfskip.com/ 2a01:4ff:1f0:dd50::1, Status -14
| https://surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4ff:1f0:dd50::1, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 195.201.128.179, Status 301
| https://www.surfskip.com/ 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 5.161.230.87, Status -14
| https://www.surfskip.com/ 5.161.47.86, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 5.161.47.86, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 195.201.128.179, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4ff:1f0:dd50::1, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4ff:f0:5f41::1, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2a01:4f8:1c1e:d6f1::1, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| https://www.surfskip.com/ 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 5.161.230.87, Status -14
| https://www.surfskip.com/ 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| K | https://www.surfskip.com/ 5.78.156.59, Status -14
| https://www.surfskip.com/ 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.201.128.179, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.47.86, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.47.86, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 195.201.128.179, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| K | http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.223.91.20, Status 301
| Configuration problem - different ip addresses with different status
|
| N | https://[2406:da1e:0214:c901:4872:9a6e:238c:6187]/ 2406:da1e:214:c901:4872:9a6e:238c:6187
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2600:1f18:6a07:0601:6471:b5e4:ef15:3b72]/ 2600:1f18:6a07:601:6471:b5e4:ef15:3b72
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2600:1f1c:06db:8800:bd8b:261d:3c09:f7b3]/ 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a01:04f8:1c1e:d6f1:0000:0000:0000:0001]/ 2a01:4f8:1c1e:d6f1::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a01:04ff:00f0:5f41:0000:0000:0000:0001]/ 2a01:4ff:f0:5f41::1
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a05:d014:179b:c400:2fc6:8141:276a:b7e9]/ 2a05:d014:179b:c400:2fc6:8141:276a:b7e9
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://[2a05:d018:1d22:0800:4a54:2b5a:cf5d:17af]/ 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://5.78.156.59/ 5.78.156.59
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://5.161.47.86/ 5.161.47.86
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://76.223.91.20/ 76.223.91.20
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| N | https://195.201.128.179/ 195.201.128.179
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
|
| 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 surfskip.com, 8 ip addresses.
|
| 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.surfskip.com, 8 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 surfskip.com, 8 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 www.surfskip.com, 8 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.surfskip.com
|
| 2. Header-Checks |
| A | expireddomains.com
| report-to
| Ok: Header without syntax errors found: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=7CoqpW8v8oqfdU%2FKxZg1i16CQmtbSzaeKWYdn2%2BO82ZCh4Bt46%2BTOVe%2Bnx09kR28qeG1ZGqyAhQIpq%2FCO1Ok3OPkiGtIkBCG3svwsgJZqfm5%2BVLPb6RmxvdRazqc%2FBpJcBlrER9izOJdqjhbFYRNPQ%3D%3D"}]}
|
| A |
|
| Ok: Header without syntax errors found: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=7CoqpW8v8oqfdU%2FKxZg1i16CQmtbSzaeKWYdn2%2BO82ZCh4Bt46%2BTOVe%2Bnx09kR28qeG1ZGqyAhQIpq%2FCO1Ok3OPkiGtIkBCG3svwsgJZqfm5%2BVLPb6RmxvdRazqc%2FBpJcBlrER9izOJdqjhbFYRNPQ%3D%3D"}]}
|
| A |
| X-Content-Type-Options
| Ok: Header without syntax errors found: nosniff
|
| A |
| Referrer-Policy
| Ok: Header without syntax errors found: strict-origin
|
| A |
| Permissions-Policy
| Ok: Header without syntax errors found: geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()
|
| A |
| X-Frame-Options
| Ok: Header without syntax errors found: DENY
|
| B |
|
| Info: Header is deprecated. May not longer work in modern browsers. DENY. 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 | expireddomains.com
| Content-Security-Policy
| Critical: Missing Header:
|
| B | expireddomains.com
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | expireddomains.com
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | expireddomains.com
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 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: ns1.dns-redirect.com, ns2.dns-redirect.com, 2 Name Servers included in Delegation: ns1.dns-redirect.com, ns2.dns-redirect.com, 2 Name Servers included in 1 Zone definitions: ns1.dns-redirect.com, ns2.dns-redirect.com, 1 Name Servers listed in SOA.Primary: ns1.dns-redirect.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.dns-redirect.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.dns-redirect.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: ns1.dns-redirect.com, ns2.dns-redirect.com
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| 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: dns-redirect.com
|
| A | Good: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, US
|
| A |
|
| A | Good: Nameserver supports TCP connections: 5 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 5 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 5 good Nameserver
|
| A | Good: All SOA have the same Serial Number
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
|
| 4. Content- and Performance-critical Checks |
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59
|
| 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.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87
|
| 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.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2406:da1e:214:c901:4872:9a6e:238c:6187, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f1c:6db:8800:bd8b:261d:3c09:f7b3, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:1f18:6a07:601:6471:b5e4:ef15:3b72, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d014:179b:c400:2fc6:8141:276a:b7e9, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:f0:5f41::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4ff:1f0:dd50::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a01:4f8:1c1e:d6f1::1, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.161.230.87, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d018:1d22:800:4a54:2b5a:cf5d:17af, Status 301
| http://www.surfskip.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 5.78.156.59, Status -14
| Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. 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://expireddomains.com/domain/surfskip.com?utm_source=redi
|
| 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://expireddomains.com/domain/surfskip.com?utm_source=redi
|
| 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.
|
| A | Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 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. 1 images (type image/png, image/jpg, image/jpeg, image/webp, image/gif) found without additional Compression. Not required because these images are already compressed
|
| A | Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 1 external CSS / JavaScript files with long Cache-Control max-age found
|
| 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. 1 image files with long Cache-Control max-age found
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Good: All img-elements have a valid alt-attribute.: 2 img-elements 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 | Info: Different Server-Headers found
|
| A | Duration: 494463 milliseconds, 494.463 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)