Check DNS, Urls + Redirects, Certificates and Content of your Website


 

 

P

 

Tls-Protocol error

 

Checked:
29.01.2019 17:06:42

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
dev.special-lite.com
A
3.16.107.165
Hostname: ec2-3-16-107-165.us-east-2.compute.amazonaws.com
yes
1
0

AAAA
2607:f1c0:1000:10a3:a1fb:3220:d458:c822

yes


www.dev.special-lite.com
A
3.16.107.165
Hostname: ec2-3-16-107-165.us-east-2.compute.amazonaws.com
yes
1
0

AAAA
2607:f1c0:1000:10a3:a1fb:3220:d458:c822

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2019, 00:00:00 +, Signature-Inception: 21.01.2019, 00:00:00 +, KeyTag 19164, Signer-Name: (root)






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2019, 00:00:00 +, Signature-Inception: 21.01.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 19164 used to validate the DNSKEY RRSet






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: com

com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.02.2019, 05:00:00 +, Signature-Inception: 29.01.2019, 04:00:00 +, KeyTag 16749, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 16749 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16883, Flags 256






Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.02.2019, 19:25:33 +, Signature-Inception: 22.01.2019, 19:20:33 +, KeyTag 30909, Signer-Name: com






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet






Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: special-lite.com

special-lite.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: dev.special-lite.com

dev.special-lite.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.dev.special-lite.com

www.dev.special-lite.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.dev.special-lite.com
  ns1052.ui-dns.org

dev.special-lite.com
  ns1052.ui-dns.org

special-lite.com
  ns1018.ui-dns.de


  ns1052.ui-dns.org


  ns1083.ui-dns.com


  ns1114.ui-dns.biz

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net

 

4. SOA-Entries

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://dev.special-lite.com/
3.16.107.165
200


0.230
H
Date: Tue, 29 Jan 2019 16:07:10 GMT
Server: Apache/2.4.29 (Ubuntu)
Last-Modified: Tue, 27 Nov 2018 14:11:08 GMT
ETag: "2aa6-57ba6055aaa53"
Accept-Ranges: bytes
Content-Length: 10918
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://dev.special-lite.com/
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
200


0.267
H
Content-Type: text/html
Content-Length: 229
Connection: close
Date: Tue, 29 Jan 2019 16:07:10 GMT
Server: Apache
Last-Modified: Tue, 20 Nov 2012 07:16:34 GMT
ETag: "e5-4cee8038ab880"
Accept-Ranges: bytes

• http://www.dev.special-lite.com/
3.16.107.165
200


0.230
H
Date: Tue, 29 Jan 2019 16:07:10 GMT
Server: Apache/2.4.29 (Ubuntu)
Last-Modified: Tue, 27 Nov 2018 14:11:08 GMT
ETag: "2aa6-57ba6055aaa53"
Accept-Ranges: bytes
Content-Length: 10918
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• http://www.dev.special-lite.com/
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
200


0.266
H
Content-Type: text/html
Content-Length: 229
Connection: close
Date: Tue, 29 Jan 2019 16:07:10 GMT
Server: Apache
Last-Modified: Tue, 20 Nov 2012 07:16:34 GMT
ETag: "e5-4cee8038ab880"
Accept-Ranges: bytes

• https://dev.special-lite.com/
3.16.107.165
200


6.373
N
Certificate error: RemoteCertificateNameMismatch
Date: Tue, 29 Jan 2019 16:07:11 GMT
Server: Apache/2.4.29 (Ubuntu)
Last-Modified: Tue, 27 Nov 2018 14:11:08 GMT
ETag: "2aa6-57ba6055aaa53"
Accept-Ranges: bytes
Content-Length: 10918
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• https://dev.special-lite.com/
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
-10


0.267
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• https://www.dev.special-lite.com/
3.16.107.165
200


6.123
N
Certificate error: RemoteCertificateNameMismatch
Date: Tue, 29 Jan 2019 16:07:18 GMT
Server: Apache/2.4.29 (Ubuntu)
Last-Modified: Tue, 27 Nov 2018 14:11:08 GMT
ETag: "2aa6-57ba6055aaa53"
Accept-Ranges: bytes
Content-Length: 10918
Vary: Accept-Encoding
Connection: close
Content-Type: text/html

• https://www.dev.special-lite.com/
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
-10


0.267
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.16.107.165
404


0.226
A
Not Found
Visible Content:
Date: Tue, 29 Jan 2019 16:07:24 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 353
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
204


0.640
A
Visible Content:
Content-Length: 0
Connection: close
Date: Tue, 29 Jan 2019 16:07:25 GMT
Server: Apache
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY

• http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.16.107.165
404


0.223
A
Not Found
Visible Content:
Date: Tue, 29 Jan 2019 16:07:24 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 357
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2607:f1c0:1000:10a3:a1fb:3220:d458:c822
204


0.500
A
Visible Content:
Content-Length: 0
Connection: close
Date: Tue, 29 Jan 2019 16:07:25 GMT
Server: Apache
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY

 

7. Comments


1. General Results, most used to calculate the result

Aname "dev.special-lite.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (8 urls)
http://dev.special-lite.com/ 3.16.107.165


Url with incomplete Content-Type - header - missing charset
http://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822


Url with incomplete Content-Type - header - missing charset
http://www.dev.special-lite.com/ 3.16.107.165


Url with incomplete Content-Type - header - missing charset
http://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822


Url with incomplete Content-Type - header - missing charset
https://dev.special-lite.com/ 3.16.107.165


Url with incomplete Content-Type - header - missing charset
https://www.dev.special-lite.com/ 3.16.107.165


Url with incomplete Content-Type - header - missing charset
Bhttps://dev.special-lite.com/ 3.16.107.165
200

Missing HSTS-Header
Bhttps://www.dev.special-lite.com/ 3.16.107.165
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
Khttps://dev.special-lite.com/ 3.16.107.165, Status 200

https://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status -10
Configuration problem - different ip addresses with different status
Khttps://www.dev.special-lite.com/ 3.16.107.165, Status 200

https://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status -10
Configuration problem - different ip addresses with different status
Khttp://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404

http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
Configuration problem - different ip addresses with different status
Khttp://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404

http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204
Configuration problem - different ip addresses with different status
Nhttps://dev.special-lite.com/ 3.16.107.165
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://www.dev.special-lite.com/ 3.16.107.165
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Phttps://dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
-10

Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)
Phttps://www.dev.special-lite.com/ 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
-10

Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome)

2. Header-Checks


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
204

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822
204

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204

http://dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
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.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:1000:10a3:a1fb:3220:d458:c822, Status 204

http://www.dev.special-lite.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.16.107.165, Status 404
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.
AGood: 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
AInfo: Different Server-Headers found
ADuration: 40804 milliseconds, 40.804 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
dev.special-lite.com
3.16.107.165
443
name does not match
Tls12
DiffieHellman
2048
Aes128
128
Sha256
not supported
ok
dev.special-lite.com
3.16.107.165
443
name does not match
Tls12

DiffieHellman
2048
Aes128
128
Sha256
not supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0


www.dev.special-lite.com
3.16.107.165
443
name does not match
Tls12
DiffieHellman
2048
Aes128
128
Sha256
not supported
ok

www.dev.special-lite.com
3.16.107.165
443
name does not match
Tls12

DiffieHellman
2048
Aes128
128
Sha256
not supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0

 

9. Certificates

1.
1.
CN=photosof.space
27.01.2019
27.04.2019
2125 days expired
photosof.space - 1 entry
1.
1.
CN=photosof.space
27.01.2019

27.04.2019
2125 days expired


photosof.space - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03F31C5CF73BEDA283AEEC626F7A90533955
Thumbprint:7AE4BE7211007BCAB565A280416F520C3E2E7BDD
SHA256 / Certificate:RldEOL1wflNtFcHOwrF6pga7EdkeB2bxdjkHZ3DiBFs=
SHA256 hex / Cert (DANE * 0 1):46574438bd707e536d15c1cec2b17aa606bb11d91e0766f17639076770e2045b
SHA256 hex / PublicKey (DANE * 1 1):c33b3ca5a5742c42d1da2de9beaf61c11c4ee4a1fccd538a4df6c7191e2a90b5
SHA256 hex / Subject Public Key Information (SPKI):c33b3ca5a5742c42d1da2de9beaf61c11c4ee4a1fccd538a4df6c7191e2a90b5
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1435 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1435 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1238 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1238 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.dev.special-lite.com
0

no CAA entry found
1
0
dev.special-lite.com
0

no CAA entry found
1
0
special-lite.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dev.special-lite.com

ok
1
0
www.dev.special-lite.com

ok
1
0
_acme-challenge.dev.special-lite.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.dev.special-lite.com

Name Error - The domain name does not exist
1
0
_acme-challenge.dev.special-lite.com.dev.special-lite.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.dev.special-lite.com.www.dev.special-lite.com

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

 

 

Permalink: https://check-your-website.server-daten.de/?i=8bff610a-9b3a-4f7e-a892-15fc206d5e8c

 

Last Result: https://check-your-website.server-daten.de/?q=dev.special-lite.com - 2019-01-29 17:06:42

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=dev.special-lite.com" target="_blank">Check this Site: dev.special-lite.com</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=dev.special-lite.com