PaulB-H / watch-sites

check if a list of domains are returning 200 status

watch-sites

Make a head request to a list of HTTPS domains and write a log of the status.

Send an email (via SMTP) if status is not 200.

Dependencies: nodemailer, dotenv

---

Usage

1. npm install

2. Create a .env file and add the following values:

DOMAINS:           A CSV list of HTTPS domains to check
SMTP_HOST:         Email SMTP Host
SMTP_PORT:         Email SMTP Port
SMTP_SECURE:       Nodemailer securee. Us 0 for port 25 or 587
  ^ 0 = false, 1 = true
EMAIL_USER:        Email address that will send the message
EMAIL_PASSWORD:    Password for sending email address
EMAIL_TO:          Email recipient 
SEND_GROUPED_MAIL: Send one email with each failed domain in the body, or send an email for each failed domain. 
  ^ 0 = false, 1 = true

example .env

DOMAINS=https://cloudflare.com,https://letsencrypt.org,https://developer.mozilla.org
SMTP_HOST=smtp.email.com
SMTP_PORT=587
SMTP_SECURE=0
EMAIL_USER=[e-mail]
EMAIL_PASSWORD=emailPass123
EMAIL_TO=[e-mail]
SEND_GROUPED_MAIL=1

3. Run with node index
4. PM2 (optional)
   1. We can use the following command from the same directory as the log will be, to make PM2 not watch the log file but watch the rest:
      pm2 start watch-sites --watch --ignore-watch="watch-sites.log"

---

About

I wanted a tool to monitor some of the sites I host on my VPS.

I wanted it to not rely on 3rd party packages. This included another attempt at getting my VPS working as a mailserver. While unsuccessful, I was able to get mail to send, just not trusted by Google. I think Ijust need to fix the rDNS/PTR records, it was able to send successfully to a throw away email service, which was pretty neat.

Initially had code to give a more interactive feedback to the console (time remaining would print over the last line instead of making a new one) but those didn't play nice with PM2, so its commented out for now. Might add back with some optional flag.

---

todo

• zip/archive/rotate the log based on time or size intervals
  • One logfile per day may work well, with options to change
• A header line in each log file with details about the log file itself?
  • Like time frame the log covers, number of entries, list of domains, but these things might be better for a log parser. Lets just make a header line with just the date period the log encompasses instead.
• Log parser to query and display the data
• How do we want to handle http request errors? Line 217

did

• Batch emails for non-200 warnings, so one email with a list of each domain and the status in the body. We could put the number of domains that failed in the subject line. ✓ Done