signalfort · from outside
SSL certificate and domain expiry monitoring
Expired HTTPS or domain means downtime and an attack signal. Perimeter hygiene is in the product — not a separate card.
- ✓Advance warning before HTTPS expires
- ✓Trust chain and hostname
- ✓Root domain registration expiry
- ✓Email when risk is hot
signalfort in numbers
Nothing to install. Enter a domain — and the check starts.
Why it hurts
Browsers scare customers, payments fail, registrars can suspend the zone. A one-off cert check is wrong two weeks later.
- —Cert expires on a weekend — nobody watching
- —Hostname in the cert does not match the site
- —Domain renewal forgotten at the registrar
- —Separate SSL tool not tied to CVE and subdomains
What we monitor
Same findings and lifecycle as vulnerabilities — not a bolt-on SSL widget.
Certificate lifetime
notAfter and advance warning before visitors see a browser error.
Chain and name
Trust chain and hostname match for what is served outside.
Domain expiry
Root registration / expiry via WHOIS/RDAP.
Weak TLS
Parameters visible from outside that should not stay in production.
How to turn it on
One TXT record — then monitoring follows the plan schedule.
- 01
Add the domain
Enter the root address in the dashboard.
- 02
Verify DNS
TXT proves the domain is yours.
- 03
Watch findings
SSL and domain appear next to other risks.
Email when risk is hot — not daily noise
One-off check vs monitoring
The difference is not reading notAfter — it is what happens two weeks later.
- Report as of a date
- Easy to forget renewal
- Not tied to perimeter
- Separate tool
- 1.Schedule by planweek or day
- 2.Alert before expiryemail
- 3.Finding in one loopwith status
- 4.Next to CVE and subsone dashboard
A fact without a PoC
SSL or domain expiry is observed directly — confidence is confirmed immediately.
Days left until notAfter
Owner assigned, email sent, deadline on the finding
- ·host and port 443
- ·notAfter date
- ·issue type
Who cares
Anyone whose site is a sales channel, not an internal stand.
Marketing / e-commerce
Expired HTTPS hits trust and conversion the same day.
IT without a SOC
No extra SSL dashboard — it lives in one dashboard.
Domain owner
Registration expiry is easy to miss across vendors.
Plans for the job
Perimeter hygiene is in every plan; frequency and depth differ.
Radar
Free
Passive analysis and weekly hygiene. One domain.
Contour
from ₽1,490/mo
Daily checks, confirmation, fix deadlines and re-check.
Business
from ₽4,490/mo
5 domains, fix deadlines, webhooks and MCP for AI assistants, FSTEC/CRA reports, deep analysis with consent.
Why we do not sell hygiene alone
Customers pay for confidence in what’s exposed: confirming risk and tracking change. SSL and domain expiry belong in the same loop as CVEs and new hosts.
A separate “SSL monitoring” SKU would add pricing noise; we rank for the search query, but in-product it stays one contour.
What we check on HTTPS
Expiry (notAfter), hostname match, basic chain correctness, and weak parameters visible from outside.
We do not scan internal PKI or VPN-only certs — only what the host serves to the internet.
Root domain expiry
Via WHOIS/RDAP we record registration expiry. A finding appears early so the domain is not lost between vendors.
Email includes the domain, days left, and a link to the cabinet. Full WHOIS is not stored without need.
Frequency by plan
Radar — weekly. Contour and Business — daily. Active perimeter checks — on paid plans after verification.
See also check a site from outside and new subdomains.
FAQ
Do I need a separate SSL monitoring product?
No. Perimeter hygiene is in every plan; only frequency differs.
Do you see internal certificates?
Only what the host serves on HTTPS from outside. Internal PKI is out of scope.
What is in the email?
Host or domain, days left, dashboard link. We do not keep full WHOIS or cert bodies without need.
Does this replace Let’s Encrypt auto-renewal?
No. We warn and track perimeter risk; issuance and renewal stay with you or the host.