pr.social

Readiness by lane

Green: pr.social. Thin bar: Social Media & Networking peer median.

Priority fixes for pr.social

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for pr.social was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   39% of Social Media & Networking peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   54% of Social Media & Networking peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   13% of Social Media & Networking peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for pr.social, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   11% of Social Media & Networking peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What pr.social already does well

Practices fewer than half of Social Media & Networking peers use.

• Content Security Policy presentContent-Security-Policy present.28% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• HTTP/3 advertisedHTTP/3 advertised.35% of peers

What we saw

Homepage checked

https://pr.social/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-03

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

12 KB, br

Images on homepage

0

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Social Media & Networking sites

• allmylinks.com81
• chitchat.gg82
• discord.com82
• fanvue.com81
• getmysocial.com82

Social Media & Networking readiness benchmark