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



H

Http as Destination - no encryption

Checked:
06.05.2019 13:48:24


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
sica-web.app
A
178.128.101.145
No Hostname found
yes
2
0

AAAA

yes


www.sica-web.app
CNAME
sica-web.app
yes
1
0

A
178.128.101.145
No Hostname found
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 25266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



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: app
app
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.05.2019, 05:00:00 +, Signature-Inception: 06.05.2019, 04:00:00 +, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 64041, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 27.05.2019, 11:40:07 +, Signature-Inception: 05.05.2019, 11:40:07 +, KeyTag 23684, Signer-Name: app



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



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

Zone: sica-web.app
sica-web.app
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "fmn6hlfp87npqub2edl59h99p9a7j3bj" between the hashed NSEC3-owner "fmn6hlfp87npqub2edl59h99p9a7j3bj" and the hashed NextOwner "fmn6m5f9lidm70inaaa9sd7vfuvpgums". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner fmn6hlfp87npqub2edl59h99p9a7j3bj.app., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 24.05.2019, 11:44:17 +, Signature-Inception: 02.05.2019, 11:44:17 +, KeyTag 64041, Signer-Name: app



0 DNSKEY RR found




Zone: www.sica-web.app
www.sica-web.app
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
sica-web.app
  ns1.digitalocean.com / 67m29
173.245.58.51

 
2400:cb00:2049:1::adf5:3a33

  ns2.digitalocean.com / 67m27
173.245.59.41

 
2400:cb00:2049:1::adf5:3b29

  ns3.digitalocean.com / 67m31
198.41.222.173

 
2400:cb00:2049:1::c629:dead
app
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com


4. SOA-Entries


Domain:app
Zone-Name:
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


Domain:sica-web.app
Zone-Name:
Primary:ns1.digitalocean.com
Mail:hostmaster.sica-web.app
Serial:1555046293
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


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://sica-web.app/
178.128.101.145
200

0.533
H
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:42 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 4674
Connection: close
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Thu, 18 Apr 2019 13:02:11 GMT
ETag: W/"1242-16a308a4eda"

• http://www.sica-web.app/
178.128.101.145
200

0.547
H
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:42 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 4674
Connection: close
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Thu, 18 Apr 2019 13:02:11 GMT
ETag: W/"1242-16a308a4eda"

• https://sica-web.app/
178.128.101.145
200

2.543
A
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:44 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 4674
Connection: close
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Thu, 18 Apr 2019 13:02:11 GMT
ETag: W/"1242-16a308a4eda"
Strict-Transport-Security: max-age=63072000; includeSubdomains
X-Frame-Options: DENY
X-Content-Type-Options: nosniff

• https://www.sica-web.app/
178.128.101.145
200

2.537
A
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:46 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 4674
Connection: close
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Thu, 18 Apr 2019 13:02:11 GMT
ETag: W/"1242-16a308a4eda"
Strict-Transport-Security: max-age=63072000; includeSubdomains
X-Frame-Options: DENY
X-Content-Type-Options: nosniff

• http://sica-web.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.128.101.145
404

0.534
A
Not Found
Visible Content:
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:48 GMT
Content-Type: text/html
Content-Length: 178
Connection: close

• http://www.sica-web.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.128.101.145
404

0.537
A
Not Found
Visible Content:
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 06 May 2019 11:48:49 GMT
Content-Type: text/html
Content-Length: 178
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "sica-web.app" is domain, public suffix is "app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc."
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
Agood: every https has a Strict Transport Security Header
Agood: HSTS max-age is long enough, 63072000 seconds = 730 days
Agood: HSTS has includeSubdomains - directive
AExcellent: Domain is in the Google-Preload-List
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):4 complete Content-Type - header (6 urls)
http://sica-web.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.101.145


Url with incomplete Content-Type - header - missing charset
http://www.sica-web.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.128.101.145


Url with incomplete Content-Type - header - missing charset
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.

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
AGood: 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.

3. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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
ADuration: 70560 milliseconds, 70.560 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
sica-web.app
178.128.101.145
443
ok
Tls12
DiffieHellman
2048
Aes256
256
Sha384
supported
ok
sica-web.app
178.128.101.145
443
ok
Tls12

DiffieHellman
2048
Aes256
256
Sha384
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
Chain - incomplete
1CN=sica-web.app

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


www.sica-web.app
178.128.101.145
443
ok
Tls12
DiffieHellman
2048
Aes256
256
Sha384
supported
ok

www.sica-web.app
178.128.101.145
443
ok
Tls12

DiffieHellman
2048
Aes256
256
Sha384
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
Chain - incomplete
1CN=sica-web.app

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


9. Certificates

1.
1.
CN=sica-web.app
11.02.2019
12.05.2019
1146 days expired
sica-web.app, www.sica-web.app - 2 entries
1.
1.
CN=sica-web.app
11.02.2019

12.05.2019
1146 days expired
sica-web.app, www.sica-web.app - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:031F20F790F40A1D7A1EFE9F0FBBD8A62569
Thumbprint:617D847CA3551AF2B1B92E1B7308E18C1F34F175
SHA256 / Certificate:kVGrfwxtHM4VoADkKo9SxiMVqIAoh3/6rBeqh+1dkhg=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d10c3c1185962bd1ec0227b84847c263c19311a9449b0780e58952e40bc3cb21
SHA256 hex / Subject Public Key Information (SPKI):d10c3c1185962bd1ec0227b84847c263c19311a9449b0780e58952e40bc3cb21
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
471 days expired


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

17.03.2021
471 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
274 days expired


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

30.09.2021
274 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" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute


12. 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.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.sica-web.app



1
0
sica-web.app
0

no CAA entry found
1
0
app
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sica-web.app

ok
1
0
www.sica-web.app


1
0
_acme-challenge.sica-web.app

missing entry or wrong length
1
0
_acme-challenge.www.sica-web.app

Name Error - The domain name does not exist
1
0
_acme-challenge.sica-web.app.sica-web.app

perhaps wrong
1
0
_acme-challenge.www.sica-web.app.www.sica-web.app

Name Error - The domain name does not exist
1
0


15. 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=7e85f372-2e4e-496e-8591-7d1931597bf8


Last Result: https://check-your-website.server-daten.de/?q=sica-web.app - 2019-05-06 13:48:24


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

<a href="https://check-your-website.server-daten.de/?q=sica-web.app" target="_blank">Check this Site: sica-web.app</a>