ourshopee.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

0High

8Medium

17Low

2Info

Collected 20 hours ago4.3sfrom cache

Certificate Transparency195
DNS resolution25
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs42
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis27

noteFound 195 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-en/
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://ourshopee.com/uae-en/
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://ourshopee.com/uae-en/
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://ourshopee.com/uae-en/
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://ourshopee.com/uae-en/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: ourshopee.com
35.154.46.183 (dev.ourshopee.com) reports nginx 1.28.0. 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: 35.154.46.183
phpmyadmin.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: phpmyadmin.ourshopee.com
kibana.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: kibana.ourshopee.com
kibana.dev.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: kibana.dev.ourshopee.com
dev.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.ourshopee.com
stage.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.ourshopee.com
api.dev.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api.dev.ourshopee.com
cdn-dev.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: cdn-dev.ourshopee.com
crm.dev.ourshopee.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: crm.dev.ourshopee.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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-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://ourshopee.com/uae-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: ourshopee.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: ourshopee.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: ourshopee.com

final https://ourshopee.com/uae-en/status 200time 1366msstack cloudflare · Next.js

✓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 AWSALB
no Secure · no HttpOnly · no SameSite
!Cookie AWSALBCORS
Secure · no HttpOnly · SameSite=none
✗Cookie country_key
no Secure · no HttpOnly · no SameSite
✗Cookie language_key
no Secure · no HttpOnly · no SameSite
✗Cookie user_pseudo_id
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 ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:admin@ourshopee.com; ruf=mailto:admin@ourshopee.com; sp=none; adkim=s; aspf=s
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
bethany.ns.cloudflare.com buck.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC11.4 years old
ourshopee.com
✓Registration expiry959 days
2029-04-23
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
bethany.ns.cloudflare.com buck.ns.cloudflare.com

Address	Ports	Edge	Network
104.26.10.46 ourshopee.com +6	80443205220532082208320862087+5	Cloudflare~	—
104.26.11.46 ourshopee.com +5	80443205220532082208320862087+5	Cloudflare~	—
172.67.75.62 ourshopee.com +5	80443205220532082208320862087+5	Cloudflare~	—
13.206.216.32 dev.ourshopee.com +4	80443	direct	—
35.154.46.183 dev.ourshopee.com +4	443	direct	—
35.154.52.185 kibana.dev.ourshopee.com	none known	direct	—

Archived URLs

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

ourshopee.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames