Linux webserver 6.8.0-49-generic #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 6 17:42:15 UTC 2 x86_64
Apache/2.4.52 (Ubuntu)
Server IP : 192.168.1.1 & Your IP : 3.145.133.121
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
canonical-livepatch.json
2.48
KB
-rw-r--r--
2024-10-20 21:33
certbot.json
3.09
KB
-rw-r--r--
2025-04-08 02:09
core.json
3.57
KB
-rw-r--r--
2025-05-09 06:14
core20.json
4.19
KB
-rw-r--r--
2025-05-07 02:44
core22.json
4.2
KB
-rw-r--r--
2025-05-01 16:14
core24.json
4.2
KB
-rw-r--r--
2025-04-18 13:04
lxd.json
8.7
KB
-rw-r--r--
2024-11-27 21:23
snapd.json
2
KB
-rw-r--r--
2025-04-29 17:24
Save
Rename
{"sequence":[{"name":"certbot","snap-id":"wy7i66qPx4neXr6m9rTh7Y40h8EhtZFh","revision":"4412","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":"4482","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":"4557","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":"4557","migrated-hidden":false,"migrated-exposed-home":false}