airforce-technology.com security report

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

60risk

Elevated

Several issues worth triaging this week.

0Critical

2High

2Medium

4Low

2Info

Collected 18 hours ago137.3sfrom cache

Certificate Transparency
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture4
Email authentication1
Certificate
Security headers3
Archived URLs
Analysis10

noteCertificate Transparency did not complete (20). Results below are partial.
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.
note1 host was identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 151.101.2.133 (airforce-technology.com), which advertise php 8.4.23. 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-2026-17544 CVE-2026-17543 CVE-2026-7260 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 151.101.2.133 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-17544 ↗CVE-2026-17543 ↗CVE-2026-7260 ↗CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 151.101.2.133
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.airforce-technology.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@airforce-technology.com"`, review the reports, then move to p=quarantine and p=reject.
asset: airforce-technology.com
151.101.2.133 (airforce-technology.com) reports php 8.4.23. 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: 151.101.2.133
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: airforce-technology.com
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://www.airforce-technology.com/
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.airforce-technology.com/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.airforce-technology.com/
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: airforce-technology.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: airforce-technology.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: airforce-technology.com

final https://www.airforce-technology.com/status 200time 518msstack cloudflare · WordPress 6.9.1

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31622400; includeSubDomains; preload
✓Content-Security-Policy
frame-ancestors 'self';
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

!Cookie datadome
Secure · no HttpOnly · SameSite=lax

✓Receives mail via 2 servers
cluster05.eu.messagelabs.com cluster05a.eu.messagelabs.com
✓SPFends in -all
v=spf1 mx ip4:91.208.117.24/32 ip4:85.115.32.0/19 ip4:86.111.216.0/21 ip4:116.50.56.0/21 ip4:208.87.232.0/21 ip4:109.231.198.169/32 a:mail-relay.attenda.com include:spf.messagelabs.com -all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓4 nameservers
ns-1143.awsdns-14.org ns-1606.awsdns-08.co.uk ns-22.awsdns-02.com ns-520.awsdns-01.net

✓Registered with Register SPA30.1 years old
airforce-technology.com
✓Registration expiry325 days
2027-07-29
✗Transfer lock
none
✓4 nameservers at registry
ns-1143.awsdns-14.org ns-1606.awsdns-08.co.uk ns-22.awsdns-02.com ns-520.awsdns-01.net

Address	Ports	CVEs	Edge	Network
151.101.130.133 airforce-technology.com +2	80443	0	direct	—
151.101.66.133 airforce-technology.com +2	80443	0	direct	—
151.101.194.133 airforce-technology.com +3	80443	0	direct	—
151.101.2.133 airforce-technology.com +3	80443	5	Cloudflare~	—

Archived URLs

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

airforce-technology.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames