ekvia.net security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

59risk

Elevated

Several issues worth triaging this week.

0Critical

1High

5Medium

4Low

2Info

Collected 7 hours ago20.1sfrom cache

Certificate Transparency15
DNS resolution15
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs19
Registration
DNS posture2
Email authentication1
Certificate
Security headers2
Archived URLs
Analysis12

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.ekvia.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@ekvia.net"`, review the reports, then move to p=quarantine and p=reject.
asset: ekvia.net
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 91.210.190.6:22
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 91.210.190.5:22
Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://ekvia.net/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://ekvia.net/
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: ekvia.net
91.210.190.6 (pve906.ekvia.net) reports openssh 10.0p2. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 91.210.190.6
91.210.190.5 (pve905.ekvia.net) reports openssh 10.0p2. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 91.210.190.5
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://ekvia.net/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: ekvia.net
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: ekvia.net
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: ekvia.net

final https://ekvia.net/status 526time 1654msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✓Referrer-Policy
same-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
mail.ekvia.net
✓SPFends in -all
v=spf1 a mx ip4:91.210.191.36 -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns.ekvia.com ns.ekvia.net

✓Registered with Center of Ukrainian Internet Names (UKRNAMES)18.3 years old
ekvia.net
✓Registration expiry275 days
2027-06-09
✗Transfer lock
none
✓2 nameservers at registry
ns.ekvia.com ns.ekvia.net

Address	Ports	Edge	Network
91.210.189.7 ns.ekvia.net +1	534431500	direct	—
91.210.190.212 sftpgo1.ekvia.net +3	804432121	direct	—
91.210.190.6 pve906.ekvia.net	221113128	direct	—
91.210.190.5 pve905.ekvia.net	221113128	direct	—
91.210.191.64 web25.ekvia.net +3	80443	direct	—
91.210.190.210 sftpgo.ekvia.net +1	80443	direct	—
91.210.191.239 sftpgo-ct.ekvia.net	21219443	direct	—
91.210.191.36 mail.ekvia.net	587	direct	—
91.210.191.17 pve355.ekvia.net	none known	direct	—
91.210.191.18 pve356.ekvia.net	none known	direct	—
91.210.190.12 dmdcv.ekvia.net	none known	direct	—
91.210.191.19 pve357.ekvia.net	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

ekvia.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames