SSLMate

Manage and monitor your HTTPS certificates the easy way. Find malicious and expiring certs with Cert Spotter. Issue certs from the sslmate command line.

[SSLMate @SSLMate]

Our Certificate Transparency Search API now includes a boolean field `revoked` indicating if a certificate is revoked.

You can also include `expand=revocation` in the query string to get additional details (revocation time, reason) in the response.

https://t.co/erlv4q3xW4

[SSLMate @SSLMate]

Cert Spotter now automatically monitors your domains for MTA-STS problems, and can automate the publication of correct MTA-STS policies. Read more on our blog: https://t.co/Zplo9bvpIa

[Filippo Valsorda @filippo.abyssdomain.expert @FiloSottile]

Cert Spotter is where it's at.

[SSLMate @SSLMate]

Cert Spotter now detects certificates which are affected by the Let's Encrypt Mass Revocation incident (https://t.co/WrKiPYKDsH).

Visit https://t.co/iyRS96LsFm to see if you need to replace any certs.

[SSLMate @SSLMate]

Introducing the new Cert Spotter: with Expiration Monitoring, Alert Fatigue Reduction, and More https://t.co/x5TgB8sp6j

[SSLMate @SSLMate]

New blog post: Elizabeth Warren's Website Uses a Foreign TLD. Hopefully She's Monitoring Certificate Transparency! https://t.co/f07tcE9Ybg

[SSLMate @SSLMate]

Introducing Cert Spotter API 1.0 - the easiest way to programmatically list a domain's certificates, powered by #CertificateTransparency: https://t.co/ap29LS7UxQ

[SSLMate @SSLMate]

New Blog Post: Yes, it's OK if GitHub Requests Certificates for Sub-Domains Delegated to Them (and you can now exclude delegated sub-domains from Cert Spotter monitoring)

https://t.co/BIml8eXh9J

[SSLMate @SSLMate]

All certificates issued through @SSLMate are already in compliance with the upcoming #CertificateTransparency deadline. There is no need for you to take action. https://t.co/ihfqGCEa2m

[Ryan Hurst @rmhrisk]

Reminder April 30th, 2018 is CT Day; All certificates issued after this date need to be logged or will have an interstitial in Chome.

[SSLMate @SSLMate]

@TheDaveCA @letsencrypt Directly using LE (or any CA's API) requires doing your own key management, expiration tracking, monitoring, and challenge responses. Doable if you want, but a lot of engineering work, esp. for multi-server deployments. We have a comparison here: https://t.co/eDRwroun08

[SSLMate @SSLMate]

Introducing SSLMate for SaaS - Get Certificates For Your Customers' Vanity Domains https://t.co/acHe3Fb982

[SSLMate @SSLMate]

How Cert Spotter Parses 255 Million Certificates: https://t.co/Vlc0KSy47V

[SSLMate @SSLMate]

@maxnystrom @FiloSottile @Cloudflare comodo[.]com is also valid, see: https://t.co/OkWXWNbLhQ

This is causing so much confusion I may need to special case comodoca[.]com.

[SSLMate @SSLMate]

@rodehoed Comodo supports several CAA identifiers, and comodo-dot-com is the first one they listed in their communication with Mozilla.

[SSLMate @SSLMate]

@EvanOH @__agwa Thanks for pointing this out! It's fixed now.

[SSLMate @SSLMate]

CAA Record Helper now lists all CAs in the Mozilla program, and can auto-generate using #CertificateTransparency:
https://t.co/Zx5mf136pX

[SSLMate @SSLMate]

SSL Pulse is tracking only 250 domains with CAA records. Let's get that number up!

https://t.co/ERs2YdQdth https://t.co/zeAoNq8NGp

[Bhushan Lokhande @BhushanLokhande]

SSL Pulse now tracks CAA adoption
https://t.co/41PfIn80ny

[SSLMate @SSLMate]

@HashtagSecurity @jennjanesko We monitor all CT logs recognized by Chrome. Note that expired certs are excluded by default.

[SSLMate @SSLMate]

Old Chrome showing ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs issued since June 1 (SSLMate unaffected) https://t.co/9KFK1alMqf

[SSLMate @SSLMate]

Why Chrome 53 is Rejecting Chase Bank's Symantec Certificate https://t.co/9KFK1alMqf #CertificateTransparency #redaction #symantec