gyford.com security report

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

84risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

8Medium

2Low

2Info

Collected 14 hours ago105.7sfrom cache

Certificate Transparency5
DNS resolution5
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs10
Registration
DNS posture2
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis14

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.

Shodan matched these CVEs against the service banners it saw on 93.93.131.3 (phil.gyford.com), which advertise openssh 9.2p1, http server 2.4.68. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2013-4365 CVE-2013-2765 CVE-2013-0942 CVE-2013-0941 CVE-2012-4360 CVE-2012-4001 CVE-2012-3526 CVE-2011-2688 CVE-2011-1176 CVE-2009-2299 CVE-2009-0796 CVE-2007-4723
What to do
Confirm the running versions on 93.93.131.3 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-4365 ↗CVE-2013-2765 ↗CVE-2013-0942 ↗CVE-2013-0941 ↗CVE-2012-4360 ↗
asset: 93.93.131.3
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.gyford.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@gyford.com"`, review the reports, then move to p=quarantine and p=reject.
asset: gyford.com
93.93.131.3 (phil.gyford.com) reports openssh 9.2p1, http server 2.4.68. 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: 93.93.131.3
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 93.93.131.3:21
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: 93.93.131.3: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: 176.126.243.225: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://www.gyford.com/
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://www.gyford.com/
The record ends in ?all, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: gyford.com
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: gyford.com
176.126.243.225 (gyford.com) reports openssh 8.9p1. 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: 176.126.243.225
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: gyford.com
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: gyford.com
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: gyford.com

final https://www.gyford.com/status 200time 3729msstack cloudflare

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer-when-downgrade
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 2 servers
in1-smtp.messagingengine.com in2-smtp.messagingengine.com
!SPFends in ?all
v=spf1 include:spf.messagingengine.com ?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
ns1.mythic-beasts.com ns2.mythic-beasts.com

✓Registered with Tucows Domains Inc.29.2 years old
gyford.com
✓Registration expiry2491 days
2033-07-03
✗Transfer lock
none
✓2 nameservers at registry
ns1.mythic-beasts.com ns2.mythic-beasts.com

Address	Ports	CVEs	Edge	Network
93.93.131.3 phil.gyford.com +4	212280110143443993995	12	direct	—
176.126.243.225 gyford.com +2	2280	0	direct	—

Archived URLs

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

gyford.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames