pixeljoint.com security report

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

73risk

Elevated

Several issues worth triaging this week.

0Critical

3High

3Medium

4Low

2Info

Collected 19 hours ago18.7sfrom cache

Certificate Transparency2
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis12

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.

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

final https://pixeljoint.com/status 200time 235msstack 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 ASPSESSIONIDSGRQBAST
Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
_dc-mx.056a4edad539.pixeljoint.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
byron.ns.cloudflare.com teagan.ns.cloudflare.com

✓Registered with GoDaddy.com, LLC22.0 years old
pixeljoint.com
✓Registration expiry1117 days
2029-09-28
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
byron.ns.cloudflare.com teagan.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.67.175.204 pixeljoint.com +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.96.87 pixeljoint.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.

pixeljoint.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames