Add MyTLS Certificate Monitor to monitoring options list

[deepzz0]

This PR adds MyTLS Certificate Monitor to Monitoring Service Options.

MyTLS Certificate Monitor: Powerful Certificate Discovery & Monitoring, Now with a Generous Free Tier!

We’re excited to introduce MyTLS Certificate Monitor—a comprehensive platform designed to streamline certificate asset discovery, monitoring, and management.

🔍 Effortless Certificate Discovery

Leveraging Certificate Transparency (CT) log data and the advanced MyTLS Radar scanning technology, our platform helps users automatically discover certificate assets.

🌐 One-Click Domain Monitoring

Easily add business domain names for monitoring with just one click. Gain full visibility into certificate statuses, expiration dates, and potential security risks.

⚙️ Flexible Enterprise-Grade Alerts

Customize alert rules and notification channels to meet your organization’s needs. Stay proactive with timely warnings before certificate-related issues impact your services.

🎁 And Here’s the Best Part—We’re Free!

Get started with no cost! MyTLS Certificate Monitor offers a free usage quota of up to 1,000 assets, making enterprise-level certificate management accessible to everyone.

Simplify your TLS/SSL certificate management today with MyTLS Certificate Monitor—where powerful functionality meets user-friendly design.

Thank you for your time.

[deepzz0]

Here are some pages from the dashboard:

[deepzz0]

Hi @bdaehlie, just a friendly follow-up on this PR.

It adds our service, cm.mytls.com, to the Monitoring Options list. We provide a free and stable SSL monitoring solution, built on twenty years of industry experience.

You can check out our live site here: https://cm.mytls.com

We're happy to make any adjustments if needed. Thanks for your review!

[aarongable]

@ludekjanda Is it acceptable to update both the base file and multiple translations at the same time like this? Obviously the new name and link text don't actually have to be translated, so I think the semantics here are fine, but I'm not sure if doing it all at once like this will mess up any of the translation pipelines.

[ludekjanda]

@ludekjanda Is it acceptable to update both the base file and multiple translations at the same time like this? Obviously the new name and link text don't actually have to be translated, so I think the semantics here are fine, but I'm not sure if doing it all at once like this will mess up any of the translation pipelines.

@aarongable It looks good to me since you don't want the new name to be translated. I'll hide it in Crowdin so it doesn't get translated. Thanks for letting me know.

[deepzz0]

Thank you @aarongable @ludekjanda for taking the time to review this PR and for handling the Crowdin translation configuration. I really appreciate your help in ensuring the new name won't be translated. Looking forward to the merge!