| 1. General Results, most used to calculate the result |
| A | name "tiktok.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: tiktok.com has 8 different ip addresses (authoritative).
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: tiktok.com has no ipv6 address.
|
| A | Good: No asked Authoritative Name Server had a timeout
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.68
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.70
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.71
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.75
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.78
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.82
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.83
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.92
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/add/comuser22.al.x 95.100.248.93
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
| Correct redirect https to https
|
| A | https://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| https://www.tiktok.com/404?fromUrl=/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Correct redirect https to https
|
| A | Good: destination is https
|
| A | Good - only one version with Http-Status 200
|
| A | Good: one preferred version: www is preferred
|
| A | Good: No cookie sent via http.
|
| A | Excellent: Domain is in the Google-Preload-List
|
| A | Excellent: Domain is in the Mozilla/Firefox-Preload-List
|
| HSTS-Preload-Status: Removed. 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)
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.68
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.70
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.71
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.75
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.78
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.82
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.83
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.92
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| A | http://www.tiktok.com/add/comuser22.al.x 95.100.248.93
| https://www.tiktok.com/add/comuser22.al.x
| Correct redirect http - https with the same domain name
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.73
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.76
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.78
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.87
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.88
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.92
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.99
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.102
|
| Missing HSTS-Header
|
| B | https://tiktok.com/add/comuser22.al.x 23.200.24.117
|
| Missing HSTS-Header
|
| B | https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
|
| Missing HSTS-Header
|
| B | https://www.tiktok.com/404?fromUrl=/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.73
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.76
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.78
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.87
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.88
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.92
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.99
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.102
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/add/comuser22.al.x 23.200.24.117
| http://www.tiktok.com/add/comuser22.al.x
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.73
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.76
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.78
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.87
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.88
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.92
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.99
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.102
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. 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.
|
| D | http://tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.200.24.117
| http://www.tiktok.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
|
| M | https://95.100.248.68/add/comuser22.al.x 95.100.248.68
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.70/add/comuser22.al.x 95.100.248.70
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.71/add/comuser22.al.x 95.100.248.71
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.75/add/comuser22.al.x 95.100.248.75
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.78/add/comuser22.al.x 95.100.248.78
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.82/add/comuser22.al.x 95.100.248.82
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.83/add/comuser22.al.x 95.100.248.83
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.92/add/comuser22.al.x 95.100.248.92
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://95.100.248.93/add/comuser22.al.x 95.100.248.93
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://95.100.248.68/add/comuser22.al.x 95.100.248.68
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.70/add/comuser22.al.x 95.100.248.70
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.71/add/comuser22.al.x 95.100.248.71
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.75/add/comuser22.al.x 95.100.248.75
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.78/add/comuser22.al.x 95.100.248.78
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.82/add/comuser22.al.x 95.100.248.82
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.83/add/comuser22.al.x 95.100.248.83
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.92/add/comuser22.al.x 95.100.248.92
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://95.100.248.93/add/comuser22.al.x 95.100.248.93
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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 tiktok.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 tiktok.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.tiktok.com
|
| 2. Header-Checks |
| A | www.tiktok.com
| Content-Security-Policy
| Ok: Header without syntax errors found: report-uri https://mon-i18n.tiktokv.com/monitor_browser/collect/batch/security/?bid=tiktok_pns&ev_type=csp&p=puNDx15QTnuGFi8i4dC8S&v=11&s=350&b=oab; report-to csp-endpoint; upgrade-insecure-requests; default-src 'self' 'unsafe-eval' 'unsafe-inline' blob: bytedance: data: wss://*.tiktok.com wss://*.tiktokv.com wss://*.tiktokv.eu wss://tiktok.com wss://tiktokv.com *.adsco.re *.adsintegrity.net *.akamaized.net *.amazonaws.com *.arkoselabs.com *.billetlugen.dk *.bing.com *.bitssec.com *.bytedapm.com *.bytedgame.com *.bytehwm-row.com *.byteicdn.com *.byteintl.com *.byteintl.net *.byteintlapi.com *.byteintlstatic.com *.bytelemon.com *.byteoversea.com *.byteoversea.net *.bytevcloudapi.com *.capcut.com *.cloudflare.com *.ctfassets.net *.doubleclick.net *.entradas.com *.evbuc.com *.eventim.de *.facebook.com *.facebook.net *.fbsbx.com *.fcdnstatic-intl.com *.fdmstatic.com *.g-p-static.com *.gauthmath.com *.giphy.com *.goofy-cdn.com *.goofy.app *.google.com *.googleapis.com *.googletagmanager.com *.gstatic.com *.hsforms.com *.hsforms.net *.ibytedtos.com *.ibyteimg.com *.isnssdk.com *.jumio.ai *.kakao.com *.lemon8-app.com *.lemon8cdn.com *.licdn.com *.linkedin.com *.midtrans.com *.muscdn.com *.musical.ly *.oecstatic.com *.omise.co *.pangle-ads.com *.paypal.com *.pipopay.com *.pipopay.eu *.pipopayment.com *.pipopayment.eu *.pipopayment.us *.redditstatic.com *.resso.me *.sgsnssdk.com *.soundon.global *.tableau.com *.tenor.com *.tiktok-row.net *.tiktok.com *.tiktok.ru *.tiktok.vn *.tiktokapis.com *.tiktokcdn-eu.com *.tiktokcdn-in.com *.tiktokcdn-us.com *.tiktokcdn.com *.tiktokcreativeone.com *.tiktokeu-cdn.com *.tiktokforbusinessoutbound.com *.tiktokglobalshop.com *.tiktokmusic.me *.tiktokshop.com *.tiktokshops.eu *.tiktokstaticb.com *.tiktokus.info *.tiktokv.com *.tiktokv.eu *.tiktokv.us *.tiktokvapp.eu *.tiktokw.eu *.tiktokw.us *.topbuzzcdn.com *.ttlivecdn.com *.ttlstatic.com *.ttwstatic.com *.vimeo.com *.vodupload.com *.yahoo.co.jp *.yhgfb-static.com *.youtube-nocookie.com *.zhiliaoapp.com accounts.google.com api.music.apple.com code.jquery.com facebook.com google.com i.ticketweb.com images.universe.com interactives.ap.org media.ticketmaster.eu newassets.hcaptcha.com play.itunes.apple.com res.cloudinary.com s1.ticketm.net static-label.frontgatetickets.com static.captchami.com t.co tikitoks.com tiktok.captchami.com tiktok.com tiktok.ua tiktok.vn tiktokfollowersfree.com tiktokv.com tx41v.arkoselabs.com unpkg.com v16-webapp-prime.tiktok.com vimeo.com web-app.goidentitas.id webcast.tiktok.com sf-website-login-bak.tiktokcdn-eu.com snssdk1233://* snssdk1180://*; script-src 'inline-speculation-rules' 'report-sample' 'unsafe-eval' 'wasm-unsafe-eval' accounts.google.com apis.google.com c.paypal.com cdn.ampproject.org cdnjs.cloudflare.com client-api.arkoselabs.com code.jquery.com connect.facebook.net developers.kakao.com googleads.g.doubleclick.net interactives.ap.org js-cdn.music.apple.com/musickit/v3/musickit.js js.hcaptcha.com js.hsforms.net lf16-cdn-tos.tiktokcdn-us.com/obj/static-tx/bric-captcha/core-captcha/ pay.google.com recaptcha.google.com s20.tiktokcdn.com s3.amazonaws.com sf16-website-login.neutral.tiktokcdn-eu.com sf16-website-login.neutral.ttwstatic.com sf16-website.neutral.tiktokcdn-eu.com sf16-website.neutral.ttwstatic.com sf16m-website-login.neutral.ttwstatic.com ssl.bing.com static.captchami.com tiktok.captchami.com tx41v.arkoselabs.com unpkg.com vimeo.com www.google.com www.googleadservices.com www.googleapis.com www.googletagmanager.com www.gstatic.com www.vimeo.com sf-website-login-bak.tiktokcdn-eu.com appleid.cdn-apple.com; worker-src www.tiktok.com/business/sw.js www.tiktok.com/coin/sw.js www.tiktok.com/creator/worker/ www.tiktok.com/embed/sw.js www.tiktok.com/firebase-messaging-sw.js www.tiktok.com/help/sw.js www.tiktok.com/legal/report/verification/uploader-oversea-crc32.js www.tiktok.com/live/creator-networks/pdf.worker.min.js www.tiktok.com/live/static/player-worker/ www.tiktok.com/risk-appeal-ocr/BlinkCardWasmSDK.worker.min.js www.tiktok.com/series/worker/ www.tiktok.com/sw.js www.tiktok.com/tiktokstudio/static/worker/ www.tiktok.com/tiktokstudio/sw.js www.tiktok.com/web-static-js/ www.tiktok.com/webapp-desktop/static/worker/
|
| B |
|
| Info: Header-Element is deprecated. report-uri https://mon-i18n.tiktokv.com/monitor_browser/collect/batch/security/?bid=tiktok_pns&ev_type=csp&p=puNDx15QTnuGFi8i4dC8S&v=11&s=350&b=oab
|
| F |
|
| Bad: default-src with "*" or a scheme found. That allows too much, don't use such a definition.
|
| F |
|
| Bad: default-src with 'unsafe-inline' or 'unsave-eval'. That's dangerous, don't use it.
|
| 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.
|
| E |
|
| Critical: No object-src defined, the default-src used as fallback allows too much. object / embed / applet shouldn't be able to load these resources.
|
| F |
|
| Critical: script-src with 'unsafe-inline' or 'unsafe-eval' and without a nonce found. That's dangerous, don't use it. If you really need one of these unsafe directives, add a nonce.
|
| A |
|
| Good: script-src without * and a scheme found.
|
| A |
|
| Good: script-src without data: schema found. Why is this important? The data: schema allows hidden code injection. Insert <script src='data:application/javascript;base64,YWxlcnQoJ1hTUycpOw=='></script> in your page and see what happens.
|
| F |
|
| Dangerous: No frame-src defined, but the default-src used as fallback allows the data: schema. That allows 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.
|
| C |
|
| Info: default-src and some other fetch directives have the same list of values. Remove the other fetch directive, default-src is used as fallback. Directives to remove: csp-endpoint
|
| F | www.tiktok.com
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | www.tiktok.com
| Referrer-Policy
| Critical: Missing Header:
|
| F | www.tiktok.com
| Permissions-Policy
| Critical: Missing Header:
|
| B | www.tiktok.com
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | www.tiktok.com
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | www.tiktok.com
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 19 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
|
| A | Info:: 19 Queries complete, 19 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.2 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 6 different Name Servers found: a12-66.akam.net, a13-67.akam.net, a18-64.akam.net, a1-97.akam.net, a6-65.akam.net, a9-66.akam.net, 6 Name Servers included in Delegation: a1-97.akam.net, a12-66.akam.net, a13-67.akam.net, a18-64.akam.net, a6-65.akam.net, a9-66.akam.net, 6 Name Servers included in 1 Zone definitions: a1-97.akam.net, a12-66.akam.net, a13-67.akam.net, a18-64.akam.net, a6-65.akam.net, a9-66.akam.net, 1 Name Servers listed in SOA.Primary: a9-66.akam.net.
|
| A | Good: Only one SOA.Primary Name Server found.: a9-66.akam.net.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: a9-66.akam.net.
|
| 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: a1-97.akam.net, a12-66.akam.net, a13-67.akam.net, a18-64.akam.net, a6-65.akam.net, a9-66.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 | Good: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 6 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.: 6 Name Servers, 1 Top Level Domain: net
|
| 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: akam.net
|
| A | Good: Name servers with different Country locations found: 6 Name Servers, 4 Countries: CA, ES, SG, US
|
| A | Info: Ipv4-Subnet-list: 6 Name Servers, 5 different subnets (first Byte): 184., 193., 2., 23., 95., 6 different subnets (first two Bytes): 184.26., 184.85., 193.108., 2.22., 23.211., 95.101., 6 different subnets (first three Bytes): 184.26.160., 184.85.248., 193.108.91., 2.22.230., 23.211.133., 95.101.36.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| A | Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 2 different subnets (first block): 2600:, 2a02:, 3 different subnets (first two blocks): 2600:1401:, 2600:1480:, 2a02:26f0:, 6 different subnets (first three blocks): 2600:1401:0001:, 2600:1401:0002:, 2600:1480:0800:, 2600:1480:4800:, 2600:1480:f000:, 2a02:26f0:0117:, 6 different subnets (first four blocks): 2600:1401:0001:0000:, 2600:1401:0002:0000:, 2600:1480:0800:0000:, 2600:1480:4800:0000:, 2600:1480:f000:0000:, 2a02:26f0:0117:0000:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 12 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 12 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
|
| 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 |
| A | Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
|
| https://www.tiktok.com/404?fromUrl=/add/comuser22.al.x
|
| 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.
|
| https://www.tiktok.com/404?fromUrl=/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| 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 | 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 | Info: Different Server-Headers found
|
| A | Duration: 248923 milliseconds, 248.923 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)