nabicix.com security report

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

48risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

3Medium

1Low

1Info

Collected 20 hours ago17.7sfrom cache

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

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.nabicix.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@nabicix.com"`, review the reports, then move to p=quarantine and p=reject.
asset: nabicix.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://www.nabicix.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://www.nabicix.com/
Nothing tells receiving mail servers which hosts may send as @nabicix.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: nabicix.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: nabicix.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: nabicix.com

final https://www.nabicix.com/status 200time 1801msstack cloudflare · WordPress 7.1

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

–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)
✓2 nameservers
brynne.ns.cloudflare.com randall.ns.cloudflare.com

✓Registered with Cloudflare, Inc.1.2 years old
nabicix.com
✓Registration expiry289 days
2027-06-23
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
brynne.ns.cloudflare.com randall.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.196.28 nabicix.com	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.76.143 nabicix.com +1	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.

nabicix.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames