Linux mail.vriendennsm.nl 6.1.0-51-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.177-1 (2026-07-16) x86_64
Apache/2.4.68 (Debian)
Server IP : 217.154.75.17 & Your IP : 216.73.216.195
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
var /
lib /
snapd /
sequence /
Delete
Unzip
Name
Size
Permission
Date
Action
certbot.json
3.09
KB
-rw-r--r--
2026-07-29 14:18
core.json
4.9
KB
-rw-r--r--
2026-04-20 19:30
core24.json
4.2
KB
-rw-r--r--
2026-05-20 17:05
snapd.json
1.95
KB
-rw-r--r--
2026-08-25 06:58
Save
Rename
{"sequence":[{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5603","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5758","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"},{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"5781","channel":"latest/stable","links":{"contact":["https://github.com/certbot/certbot/issues"],"website":["https://certbot.eff.org"]},"contact":"https://github.com/certbot/certbot/issues","title":"certbot","summary":"Automatically configure HTTPS using Let's Encrypt","description":"The objective of Certbot, Let's Encrypt, and the ACME (Automated\nCertificate Management Environment) protocol is to make it possible\nto set up an HTTPS server and have it automatically obtain a\nbrowser-trusted certificate, without any human intervention. This is\naccomplished by running a certificate management agent on the web\nserver.\n\nThis agent is used to:\n - Automatically prove to the Let's Encrypt CA that you control the website\n - Obtain a browser-trusted certificate and set it up on your web server\n - Keep track of when your certificate is going to expire, and renew it\n - Help you revoke the certificate if that ever becomes necessary.\n"}],"current":"5781","migrated-hidden":false,"migrated-exposed-home":false}