Overview / Backup / Staging VM

Backup / Staging VM

ssh root@206.189.206.251 — the "backup virtual machine someone just created."

DigitalOcean · NYC1 Ubuntu 24.04.3 LTS LAMP empty / unused
Verdict: this is not a backup of anything

Despite the label, this box contains no Hatch data. It is a fresh, default WordPress install with placeholder content (blog title "Temp", admin email temp@example.com, the default 2025 theme, a single user, and only the stock 12 database tables). It looks like a blank staging server spun up for a migration that was never completed — most likely intended to receive a site via the All-in-One WP Migration plugin.

System overview

Hostnameubuntu-s-1vcpu-512mb-10gb-nyc1
OSUbuntu 24.04.3 LTS
Sizing1 vCPU · 512 MB RAM · 2 GB swap · 8.7 GB disk (74% used) — very small
Uptime~19 days (created mid-May 2026)
StackApache 2 · MariaDB 10.11.14 · PHP 8.3.6

What's actually on it

Web root/var/www/html — a single WordPress 6.9.4 install (87 MB total)
Apache vhostStock 000-default.confDocumentRoot /var/www/html, no ServerName (responds on the bare IP)
Site URLhttp://206.189.206.251 (no domain pointed at it; HTTP only)
DatabaseMariaDB DB wordpress, prefix wp_, 12 tables (default), 1 user
ContentTitle "Temp", admin temp@example.com, theme twentytwentyfive — default install, no Hatch content
Pluginsakismet, all-in-one-wp-migration + its unlimited extension, stock hello.php
Backups present?None — the ai1wm-backups/ folder holds only the plugin's placeholder files, no .wpress archive

Listening ports

PortServiceScope
22SSH (OpenSSH)Public
80ApachePublic
3306MariaDBlocalhost only

Ports are clean — MariaDB is correctly bound to localhost, unlike the production droplet.

Recommendation

Because this VM holds nothing of value and isn't serving any domain, it is currently pure cost with no function. Decide one of:

  • Repurpose it as a real staging environment (point a staging. subdomain at it, import a current site, add TLS), or
  • Destroy the droplet to stop paying for it.

The All-in-One WP Migration "unlimited extension" being installed suggests someone began a migration here — worth a quick check with whoever created it before deleting.

Audited via live read-only SSH on 2026-06-08.