naseehamath.com security report

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

70risk

Elevated

Several issues worth triaging this week.

0Critical

2High

5Medium

4Low

2Info

Collected 11 hours ago375msfrom cache

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

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.

Nothing tells receiving mail servers which hosts may send as @naseehamath.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: naseehamath.com
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.naseehamath.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@naseehamath.com"`, review the reports, then move to p=quarantine and p=reject.
asset: naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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://naseehamath.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: naseehamath.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: naseehamath.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: naseehamath.com

final https://naseehamath.com/status 200time 93msstack 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
no Secure · no HttpOnly · SameSite=lax
✗Cookie laravel_session
no Secure · HttpOnly · SameSite=lax

✓Receives mail via 1 server
smtp.google.com
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

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

✓Registered with GoDaddy.com, LLC11.6 years old
naseehamath.com
✓Registration expiry2699 days
2034-01-27
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
rob.ns.cloudflare.com vera.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.200.194 naseehamath.com +2	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.42.50 naseehamath.com +2	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.

naseehamath.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames