11 things about your website you need to keep in a secure location.
The first step of any disaster recovery plan is to record all the important information you might need in the event of an emergency. Here are the top 11.
Your Server Control Panel Login Information
Whether you use cPanel, Plesk, ServerCP, or some other control panel, you have to login to access the control panel. Be sure to record not only the login ID and password, but the URL for your login access. Sometimes, this may include a port, so don’t forget to include that information as well.
Your Domain Registrar Login Information
If you are moving from one server to another, you will probably need to change your nameservers. To do that, you will need to login to your Domain Registrar’s control panel to make those changes, so be sure to record your login ID, your password, and the URL you use to login.
Your DNS Login Information
If you host your own nameservers, you will not need this information. Also, if you use your registrar’s name servers, you will not need this information. However, after the recent GoDaddy debacle, I would recommend against this. If you use an external DNS service, then you should record your login ID, password, and the URL you use to login.
Your Server IP Address
If you host your own nameservers, this will not be important for any of your configuration, but you should still have it recorded. If you use your registrar’s nameservers or another nameserver, then you will need the server IP address to record in your “A” record.
Your NameServer Information
You should have at least two nameservers — sometimes more. Typically, the protocol would be ns1.domain.com, ns2.domain.com, ns3.domain.com, etc. Some nameservers do not use ns1. but instead use simply ns. Regardless, of the format or how many you have, be sure to record all of them as they are important.
Your Database Information
You will need this for two different purposes.
#1 In case you ever need to re enter it. You will need the database name, the database username, and the database password.
Remember when you initially set up your website? If not, set up a test website to see what information is needed to confirm this.
#2 If you use a program to directly access your MySQL database tables. Personally, I use Navicat because I find that it is so much
easier to use than PhpMyAdmin. Regardless, of which one you use, you will need to record your database name, database username,
and your database password.
Be sure to record your main admin login information — both username and password. You didn’t use “Admin” as your admin login ID did you? If you did, now is your chance to change that. Install UserName Changer from the WordPress repository and make that change NOW, before you take another step.
Next, record your FTP login information. This will include your hostname (domain.com), your username, and password. Also, be sure to note whether you use standard FTP or if you operate through SSH (SFTP) access. Finally, if you use any type of encryption instead of the plain FTP, be sure to make note of that as well.
WordPress Authentication Unique Keys and Salts
Remember that long string of numbers that you generated at WordPress’s Secret Key Service? Be sure to revisit your wp-config.php file and record that string as well.
If you are not hosting your own nameservers or if you are using another mail service, you should record your MX Record settings. This would be important to continue to send and receive email should your move your website or you suffer a catastrophe.
Mail Server Information
If you host your own mail server — such as Squirrel Mail or some other service — then record your online mail server access information. This should include your login ID and password, as well as the URL that you visit to access your email. If you have to designate a specific port to access your mailbox, be sure to record it as well.
If you forward your email to a Google or GMail account like I do, then you should also record your access information for that account