swifteq.com security report

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

61risk

Elevated

Several issues worth triaging this week.

0Critical

1High

5Medium

4Low

2Info

Collected 5 hours ago5.2sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs3
Registration
DNS posture3
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis12

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.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://swifteq.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://swifteq.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://swifteq.com/
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://swifteq.com/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://swifteq.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: swifteq.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://swifteq.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://swifteq.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://swifteq.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: swifteq.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: swifteq.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: swifteq.com

final https://swifteq.com/status 202time 1196msstack 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 nevercache-b39818
no Secure · no HttpOnly · no SameSite

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com include:eu.mailgun.org include:mailgun.org include:mail.zendesk.com include:swifteq.com.spf.auto.dnssmarthost.net ~all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; fo=1; ri=3600; adkim=s; aspf=s; rua=mailto:3ca108a@dmarc.mailgun.org,mailto:6cbbb722@inbox.ondmarc.com,mailto:dmarc_agg@vali.email; ruf=mailto:3ca108a@dmarc.mailgun.org,mailto:6cbbb722@inbox.ondmarc.com,mailto:dmarc_agg@vali.email;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns0.reg365.net ns1.reg365.net ns2.reg365.net

✓Registered with Register SPA6.3 years old
swifteq.com
✓Registration expiry256 days
2027-05-21
✗Transfer lock
none
✓3 nameservers at registry
ns0.reg365.net ns1.reg365.net ns2.reg365.net

Address	Ports	CVEs	Edge	Network
35.214.45.58 swifteq.com +2	8044318765	0	direct	—

Archived URLs

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

swifteq.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames