aerospace-communications.com security report

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

57risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

4Low

1Info

Collected 10 hours ago4.9sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs2
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis10

noteCertificate Transparency did not complete (HTTP 502). 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.

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.aerospace-communications.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@aerospace-communications.com"`, review the reports, then move to p=quarantine and p=reject.
asset: aerospace-communications.com
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://aerospace-communications.com/en
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://aerospace-communications.com/en
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://aerospace-communications.com/en
Nothing tells receiving mail servers which hosts may send as @aerospace-communications.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: aerospace-communications.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://aerospace-communications.com/en
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://aerospace-communications.com/en
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://aerospace-communications.com/en
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: aerospace-communications.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: aerospace-communications.com

final https://aerospace-communications.com/enstatus 200time 955msstack cloudflare

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

!Cookie XSRF-TOKEN
Secure · no HttpOnly · SameSite=lax
✓Cookie aerospace_communications_session
Secure · HttpOnly · SameSite=lax

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
pdns03.domaincontrol.com pdns04.domaincontrol.com

✓Registered with GoDaddy.com, LLC9.0 years old
aerospace-communications.com
✓Registration expiry348 days
2027-08-21
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns37.domaincontrol.com ns38.domaincontrol.com pdns03.domaincontrol.com pdns04.domaincontrol.com

Address	Ports	CVEs	Edge	Network
35.222.244.42 aerospace-communications.com +1	80443	0	direct	—

Archived URLs

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

aerospace-communications.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames