Skip to content

EIDOS Global WordPress Site

The public corporate site for the Eidos Global brand at eidos-global.com. WordPress.

Field Value
Public URL https://eidos-global.com
Admin URL https://eidos-global.com/wp-admin/ [CONFIRM]
Audience public — Eidos Global prospects, customers, partners
Criticality medium-high [CONFIRM]
Maturity [INFO NEEDED]
Owner [INFO NEEDED]
Last reviewed 2026-05-05

1. At a glance

The Eidos Global brand's public website. WordPress on Dokploy (E2 = 145.241.230.130). Apex DNS points direct to E2, bypassing E1 Caddy. projecteidos.com 301-redirects here too, so this site doubles as the corporate front for both brands.

2. Business purpose

Brand presence and lead generation for the Eidos Global business unit (parent of the UK / IN CRMs and PE Workforce tenant).

3. Audience

Public internet.

4. Hosting & cloud infrastructure

  • Server: E2 EIDOSDev1 Dokploy VPS (145.241.230.130)
  • Deploy method: Dokploy
  • Reverse proxy: Traefik on E2 (apex DNS direct to E2)

Infrastructure map

Item Value Notes
Public hostname eidos-global.com (apex) + www. (CNAME → apex)
Backend host E2 shared with 8 other apps
Public IP 145.241.230.130
Open ports 443, 80 HTTP/3 advertised via Traefik
TLS cert Let's Encrypt via Traefik [CONFIRM]
Web server (in container) Apache/2.4.66 (Debian)
PHP version (in container) 8.3.30
WordPress version [INFO NEEDED]
Database MySQL/MariaDB container [CONFIRM]

Credentials in Vault

Secret type Vault path / link Last rotated
WordPress admin login [INFO NEEDED]
Database / wp-config.php [INFO NEEDED]
SFTP / SSH [INFO NEEDED]
Plugin/theme license keys [INFO NEEDED]
SMTP credentials [INFO NEEDED]

5. Technology behind it

WordPress (off-the-shelf) + custom theme/content.

6. Data it handles

Same as PE WordPress: contact-form PII, possibly newsletter sign-ups, no payments unless e-commerce is enabled.

7. External dependencies

DNS, CDN, mailer, plugins. [INFO NEEDED]

8. Authentication & access

WordPress local admin accounts [CONFIRM]. MFA status [INFO NEEDED].

9. Maturity assessment

[INFO NEEDED]

10. Known risks & vulnerabilities

  • [CONFIRM] Outdated plugins / themes are the #1 WordPress compromise vector.
  • [CONFIRM] /wp-login.php is brute-forced; needs WAF or rate-limiting.
  • [INFO NEEDED] MFA on admin accounts.
  • [INFO NEEDED] Backup + tested restore.
  • [INFO NEEDED] If hosted on the same server as PE WordPress, a compromise on one likely exposes the other.

11. Impact if it goes down

Brand damage, lost lead submissions. No internal blockers expected.

12. Owner & on-call

[INFO NEEDED]