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



N

No trusted Certificate

Checked:
04.07.2019 17:27:37


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
websteady.pl


yes
9
9
www.websteady.pl


yes
9
9
websteady.pl
A
91.211.222.86
Częstochowa/Silesia/Poland (PL) - TRUSTNET
No Hostname found
no


www.websteady.pl
A
91.211.222.86
Częstochowa/Silesia/Poland (PL) - TRUSTNET
No Hostname found
no



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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 25266, Flags 256



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2019, 00:00:00 +, Signature-Inception: 01.07.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: pl
pl
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.07.2019, 05:00:00 +, Signature-Inception: 04.07.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 39205, Flags 256



Public Key with Algorithm 8, KeyTag 44893, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 02.08.2019, 12:00:00 +, Signature-Inception: 03.07.2019, 12:00:00 +, KeyTag 25412, Signer-Name: pl



RRSIG-Owner pl., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 02.08.2019, 12:00:00 +, Signature-Inception: 03.07.2019, 12:00:00 +, KeyTag 44893, Signer-Name: pl



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



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



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

Zone: websteady.pl
websteady.pl
0 DS RR in the parent zone found

Zone: www.websteady.pl
www.websteady.pl
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.websteady.pl
 

websteady.pl
 

pl
  a-dns.pl / Polish ccTLD infrustructure


  b-dns.pl / b-decix


  c-dns.pl


  d-dns.pl / Polish ccTLD infrustructure


  e-dns.pl / Polish ccTLD infrastructure


  f-dns.pl


  g-dns.pl


T  h-dns.pl


  i-dns.pl


4. SOA-Entries


Domain:pl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:pl
Zone-Name:
Primary:a-dns.pl
Mail:dnsmaster.nask.pl
Serial:1562220101
Refresh:900
Retry:300
Expire:2592000
TTL:3600
num Entries:4


Domain:pl
Zone-Name:
Primary:a-dns.pl
Mail:dnsmaster.nask.pl
Serial:1562248839
Refresh:900
Retry:300
Expire:2592000
TTL:3600
num Entries:4


Domain:websteady.pl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.websteady.pl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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://websteady.pl/
91.211.222.86
301
https://websteady.pl/
1.780
A
Date: Thu, 04 Jul 2019 15:29:34 GMT
Server: Apache
X-Redirect-By: WordPress
Upgrade: h2,h2c
Connection: Upgrade, close
Location: https://websteady.pl/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://www.websteady.pl/
91.211.222.86
301
https://websteady.pl/
0.333
E
Date: Thu, 04 Jul 2019 15:29:36 GMT
Server: Apache
X-Redirect-By: WordPress
Upgrade: h2,h2c
Connection: Upgrade, close
Location: https://websteady.pl/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• https://www.websteady.pl/
91.211.222.86
301
https://websteady.pl/
0.650
N
Certificate error: RemoteCertificateNameMismatch
Date: Thu, 04 Jul 2019 15:29:38 GMT
Server: Apache
X-Redirect-By: WordPress
Upgrade: h2,h2c
Connection: Upgrade, close
Location: https://websteady.pl/
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• https://websteady.pl/
91.211.222.86
200

1.033
N
Certificate error: RemoteCertificateNameMismatch
Date: Thu, 04 Jul 2019 15:29:37 GMT
Server: Apache
Link: <https://websteady.pl/wp-json/>; rel="https://api.w.org/", <https://websteady.pl/>; rel=shortlink
Upgrade: h2,h2c
Connection: Upgrade, close
Vary: Accept-Encoding
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

• http://www.websteady.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.211.222.86
301
http://websteady.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.330
D
Visible Content:
Date: Thu, 04 Jul 2019 15:29:39 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
X-Redirect-By: WordPress
Upgrade: h2,h2c
Connection: Upgrade, close
Location: http://websteady.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://websteady.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
91.211.222.86
404

0.393
A
Not Found
Visible Content:
Date: Thu, 04 Jul 2019 15:29:39 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <https://websteady.pl/wp-json/>; rel="https://api.w.org/"
Upgrade: h2,h2c
Connection: Upgrade, close
Vary: Accept-Encoding
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

7. Comments


1. General Results, most used to calculate the result

Aname "websteady.pl" is domain, public suffix is "pl", top-level-domain-type is "country-code", Country is Poland, tld-manager is "Research and Academic Computer Network"
Agood: All ip addresses are public addresses
Agood: destination is https
Agood - only one version with Http-Status 200
Agood: one preferred version: non-www is preferred
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://websteady.pl/ 91.211.222.86
301
https://websteady.pl/
correct redirect http - https with the same domain name
Bhttps://websteady.pl/ 91.211.222.86
200

Missing HSTS-Header
Bhttps://www.websteady.pl/ 91.211.222.86
301

Missing HSTS-Header
Dhttp://www.websteady.pl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.211.222.86
301
http://websteady.pl/.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.
Ehttp://www.websteady.pl/ 91.211.222.86
301
https://websteady.pl/
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.
Nhttps://websteady.pl/ 91.211.222.86
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://www.websteady.pl/ 91.211.222.86
301
https://websteady.pl/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 9 good Nameserver
XNameserver Timeout checking Echo Capitalization: h-dns.pl
XNameserver Timeout checking EDNS512: h-dns.pl


Nameserver doesn't pass all EDNS-Checks: h-dns.pl: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
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: 134147 milliseconds, 134.147 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
websteady.pl
91.211.222.86
443
name does not match
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
supported
ok
websteady.pl
91.211.222.86
443
name does not match
Tls12

ECDH Ephermal
256
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 - too much certificates, don't send root certificates
1CN=websteady.pl.michalpuk23.smarthost.pl

2CN="cPanel, Inc. Certification Authority", O="cPanel, Inc.", L=Houston, C=US, ST=TX

3CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, C=GB, ST=Greater Manchester


www.websteady.pl
91.211.222.86
443
name does not match
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
supported
ok

www.websteady.pl
91.211.222.86
443
name does not match
Tls12

ECDH Ephermal
256
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 - too much certificates, don't send root certificates
1CN=websteady.pl.michalpuk23.smarthost.pl

2CN="cPanel, Inc. Certification Authority", O="cPanel, Inc.", L=Houston, C=US, ST=TX

3CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, C=GB, ST=Greater Manchester


9. Certificates

1.
1.
CN=websteady.pl.michalpuk23.smarthost.pl
30.06.2019
29.09.2019
1047 days expired
websteady.pl.michalpuk23.smarthost.pl, www.websteady.pl.michalpuk23.smarthost.pl - 2 entries
1.
1.
CN=websteady.pl.michalpuk23.smarthost.pl
30.06.2019

29.09.2019
1047 days expired
websteady.pl.michalpuk23.smarthost.pl, www.websteady.pl.michalpuk23.smarthost.pl - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:5DA30FABE68E0C68998E73F566041AD7
Thumbprint:DF5E676FB3F26A8D72C9D467DFB9965795C45269
SHA256 / Certificate:zGCIyCnY3oTiaebfdgmrIF/Kzh+RbXOo+KfjkVB0riA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3a5c2fd646433cc4bdc38cde8a408f0b245ab386c03101721cf7c7ad0172388f
SHA256 hex / Subject Public Key Information (SPKI):3a5c2fd646433cc4bdc38cde8a408f0b245ab386c03101721cf7c7ad0172388f
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.comodoca.com
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="cPanel, Inc. Certification Authority", O="cPanel, Inc.", L=Houston, S=TX, C=US
18.05.2015
18.05.2025
expires in 1011 days


2.
CN="cPanel, Inc. Certification Authority", O="cPanel, Inc.", L=Houston, S=TX, C=US
18.05.2015

18.05.2025
expires in 1011 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:00F01D4BEE7B7CA37B3C0566AC05972458
Thumbprint:764D2FA59ED123F9C95570C403C92FEF338EA745
SHA256 / Certificate:ghzFXOfsXHT+u0L2JOtqNsR4IVox7Wfjz3I6Z+jHXro=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):84e175ba988efb17af9c3110d77837698dccdd4a9ae3844de6b565c2f536582f
SHA256 hex / Subject Public Key Information (SPKI):84e175ba988efb17af9c3110d77837698dccdd4a9ae3844de6b565c2f536582f
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.comodoca.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


3.
CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB
19.01.2010
19.01.2038
expires in 5640 days


3.
CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB
19.01.2010

19.01.2038
expires in 5640 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA384 With RSA Encryption
Serial Number:4CAAF9CADB636FE01FF74ED85B03869D
Thumbprint:AFE5D244A8D1194230FF479FE2F897BBCD7A8CB4
SHA256 / Certificate:UvDhxOWOxikpG2AxfwdGcbhdfqgNWwcnNGNTSzK0AjQ=
SHA256 hex / Cert (DANE * 0 1):52f0e1c4e58ec629291b60317f074671b85d7ea80d5b07273463534b32b40234
SHA256 hex / PublicKey (DANE * 1 1):82b5f84daf47a59c7ab521e4982aefa40a53406a3aec26039efa6b2e0e7244c1
SHA256 hex / Subject Public Key Information (SPKI):82b5f84daf47a59c7ab521e4982aefa40a53406a3aec26039efa6b2e0e7244c1
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 - CT-Log entries found


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
pl



9
9


14. TXT - Entries

No TXT entries found


15. DomainService - Entries (alpha - see server-daten.de)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks (OpenRelayCheck is alpha) (Some changes - now checks domain + ip address, results older 2022-07-31 15:00 may be wrong / invisible)

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=39d2c9fa-69ee-4275-bb47-4c20d9e1a85a


Last Result: https://check-your-website.server-daten.de/?q=websteady.pl - 2019-07-04 17:27:37


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

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