namamia.com security report

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

62risk

Elevated

Several issues worth triaging this week.

0Critical

1High

5Medium

5Low

1Info

Collected 21 hours ago14.1sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis12

noteCertificate Transparency did not complete (HTTP 404). 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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.namamia.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@namamia.com"`, review the reports, then move to p=quarantine and p=reject.
asset: namamia.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://namamia.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://namamia.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://namamia.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://namamia.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: namamia.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://namamia.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://namamia.com/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://namamia.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://namamia.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: namamia.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: namamia.com

final https://namamia.com/status 200time 51msstack cloudflare · PHP/5.4.16

✓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 namacekcoms
no Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
!SPFends in ?all
v=spf1 a mx a:namamia.com ip4:139.162.49.144 ip6:2400:8901::f03c:91ff:fee7:982b ?all
✗DMARC
no record
–MTA-STSn/a

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

✓Registered with NameCheap, Inc.11.6 years old
namamia.com
✓Registration expiry144 days
2027-01-28
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
brad.ns.cloudflare.com ulla.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
104.21.46.45 namamia.com +2	80443205220532082208320862087+5	0	Cloudflare~	—
172.67.223.159 namamia.com +3	80443205220532082208320862087+5	0	Cloudflare~	—

Archived URLs

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

namamia.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames