Cookies Policy

When accessing the TuringSign TLS Portal, we and/or third parties may use cookies. The TLS Portal cookie policy is derived from the original policy of our strategic partner WISeKey SA, which applies to users accessing our TLS/SSL Portal.

What is a Cookie?

Lines.

A cookie is a small piece of data (text file) that a website – when visited by a user – asks your browser to store on your device in order to remember information about you, such as your language preference or login information. Those cookies are set by us and called first party cookies. We also use third party cookies – which are cookies from a domain different than the domain of the website you are visiting – for our advertising and marketing efforts.
More specifically, we use cookies and other tracking technologies for the following purposes:

Assisting you in navigation;
Assisting in registration to our events, login, and your ability to provide feedback;
Analyzing your use of our products, services or applications;
Assisting with our promotional and marketing efforts. (including behavioral advertising)

Below is a detailed list of the cookies we use on our Website. Our Website is scanned with our cookie scanning tool regularly to maintain a list as accurate as possible.

Cookie List

Necessary Cookie

These are essential cookies that do not require consent.

__hs_opt_out

This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.

This cookie is set when you give visitors the choice to opt out of cookies.

It contains the string “yes” or “no”.

It expires in 6 months.

__hs_do_not_track

This cookie can be set to prevent the tracking code from sending any information to HubSpot.

It contains the string “yes”.

It expires in 6 months.

__hs_initial_opt_in

This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.

It contains the string “yes” or “no”.

It expires in seven days.

__hs_cookie_cat_pref

This cookie is used to record the categories a visitor consented to.

It contains data on the consented categories.

It expires in 6 months.

hs_ab_test

This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.

It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.

It expires at the end of the session.

<id>_key

When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.

The cookie name is unique for each password-protected page.

It contains an encrypted version of the password so future visits to the page will not require the password again.

It expires in 14 days.

hs-messages-is-open

This cookie is used to determine and save whether the chat widget is open for future visits.

It is set in your visitor’s browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.

If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.

It contains a boolean value of True if present.

It expires in 30 minutes.

hs-messages-hide-welcome-message

This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.

It contains a boolean value of True or False.

It expires in one day. 

__hsmem

This cookie is set when visitors log in to a HubSpot-hosted site.

It contains encrypted data that identifies the membership user when they are currently logged in.

It expires in one year. 

hs-membership-csrf

This cookie is used to ensure that content membership logins cannot be forged.

It contains a random string of letters and numbers used to verify that a membership login is authentic.

It expires at the end of the session.

hs_langswitcher_choice

This cookie is used to save a visitor’s selected language choice when viewing pages in multiple languages.

It is set when a visitor selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future if they are available.

It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be “EN-US:hubspot.com”.

It expires in two years.

__cfruid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session. Learn more about Cloudflare cookies

__cf_bm

This cookie is set by HubSpot’s CDN provider and is a necessary cookie for bot protection. It expires in 30 minutes. Learn more about Cloudflare cookies

Analytics Cookies

These are non-essential cookies controlled by the cookie banner. If you’re a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.

__hstc

The main cookie for tracking visitors.

It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).

It expires in 6 months.

hubspotutk

This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts.

It contains an opaque GUID to represent the current visitor.

It expires in 6 months.

__hssc

This cookie keeps track of sessions.

This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.

It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.

It expires in 30 minutes.

__hssrc

Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.

If this cookie does not exist when HubSpot manages cookies, it is considered a new session.

It contains the value “1” when present.

It expires at the end of the session.

For the most current and comprehensive information, we encourage you to consult the official cookie policy of WISeKey SA at the following link: Click here!

0
    0
    Your Cart
    Your cart is empty

    Trustworthy AI for Better SSL

    TuringSign is actively innovating in cutting-edge AI technology to make traditional SSL workflows quicker, more efficient, more accurate and less costly.

    We apply automation to routine tasks including technical support and high assurance organization validation. This not only saves time but also minimizes errors and ensures faster, more reliable support for TuringSign users. With AI handling routine queries and tasks, your team can focus on more complex issues.

    Automation for Unmatched Speed

    Check mark with hand icon.

    Full Automation

    Fully Automate your SSL Management with ACME

    Analysis analytics column graphic improvement icon.

    Fastest OCSP

    Boost Page Loading Speeds with our Industry-Leading OCSP

    Achievement icon.

    Priority Validation

    Get High-Assurance Certificates Faster than ever

    Best Value Pricing

    Lowest Prices for Best-in-Class Products : Affordability with excellence.

    Standard DV SSL

    DigiCert $64
    Sectigo $99
    GlobalSign $249
    GoDaddy $69
    TuringSign $59

    Wildcard DV SSL

    DigiCert $629
    Sectigo $499
    GlobalSign $849
    GoDaddy $349
    TuringSign $259

    Single OV SSL

    DigiCert $312
    Sectigo $199
    GlobalSign $349
    Entrust $199
    TuringSign $179

    Wildcard OV SSL

    DigiCert $984
    Sectigo $879
    GlobalSign $949
    Entrust $799
    TuringSign $699

    EV SSL

    DigiCert $468
    Sectigo $279
    GlobalSign $599
    GoDaddy $399
    TuringSign $209

    Source: Netcraft SSL Server Survey, August 2024. Provided for reference only. 3rd Party prices may have change.

    Join the Waitlist

    Next Steps

    1. Validate Domain (Authenticate domain depending on which method you choose)

    Check the email that has been sent to you. To confirm the domain ownership rights for your certificate, you need to copy the validation code from the approval email, follow the link in it and paste the validation code into the corresponding field.

    From the email, please click the link to the verification page, Once in the verification page, please enter the code provided in the email for verification.

    That’s it!

    After you have completed verification, a confirmation email will be sent to you. And shortly after, an issue confirmation will be sent to you via email. You can follow the link to the portal to download your newly issued certificate.

    If you have followed the steps above and did not receive an approval email to your mailbox, please click the link to the portal and double check your validation method or contact us for help. 

    Another way of verifying a domain is DNS (TXT record) Verification. If you selected DNS Authentication as your verification method, you will receive a unique TXT record via email consisting of two parts:

    • 1. Name: Name/Host/Alias/TXT: Blank or @
    • 2. Value/Points to/Destination:”wisekey=XXXXXXX”
    • TTL: This is your TTL (Time-To-Live) value. Set it to 3600 or lower.

    Verify by adding a TXT record in your DNS. Please verify and check if you have added the correct record

    Please submit a requestfor support if you face any issues.

    Depending on your DNS provider, You may have to wait for at least an hour for the changes to take effect in the DNS Servers. You will be notified via email when the domain is verified.

    The third method of verifying a domain is HTTP File Upload Verification. After choosing File Authentication as your verification method, you will receive an email and be asked to download a unique verification file (Format: .txt) and upload it to a specific directory on your web server.



    Verify by uploading the attached file fileauth.txt in your web server as follows:



    • 1. Download the text file fileauth.txt (attached with the email).
    • 2. Upload the above file (fileauth.txt) to your host in this EXACT path: http://my-domain.com/.well-known/pki-validation/fileauth.txt


    You may have to wait for at least an hour for the changes to take effect in the validation services. You will be notified via email when the domain is verified.

    Please submit a request for support if you face any issues.

    2. Receive Confirmation (After validation an email will be sent with a link to certificate)

    3. Download certificate and upload to hosting

    Notice: After generating a CSR,
    1. Copy the Private KEY and keep this to yourself for reference.
    2. Copy only the CSR above and use(paste)
    in to request your TS Certificate.
    3. Click the top left button to close.

    TuringSign
    Privacy Overview

    This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.