Skip to content
https://peerpush.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 8 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.8.159: lookup 104.21.8.159: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 172.67.139.179: lookup 172.67.139.179: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3036::ac43:8bb3: lookup 2606:4700:3036::ac43:8bb3: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3032::6815:89f: lookup 2606:4700:3032::6815:89f: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

84
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Document and assets on Cloudflare
REVIEW
Document and assets on Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a59d5e4eacc26eed-CDG
Info::
Assets on Cloudflare: peerpush.com (assets: 146), cache REVALIDATED
Got: cf-ray: a59d60398ad700a2-CDG
Info::
Assets on Cloudflare: static.peerpush.com (assets: 26), cache DYNAMIC
Got: cf-ray: a59d603989ca3388-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a59d5e4eacc26eed-CDG

Asset hosts on a CDN

  • peerpush.com — Cloudflare · assets: 146 · Cache Status: REVALIDATED
  • static.peerpush.com — Cloudflare · assets: 26 · Cache Status: DYNAMIC

Other asset hosts

  • analytics.twitter.com — assets: 2 · below probe threshold
  • cdn.affonso.io — assets: 2 · below probe threshold
  • t.co — assets: 2 · below probe threshold
  • client.crisp.chat — assets: 1 · below probe threshold
  • static.ads-twitter.com — assets: 1 · below probe threshold
  • static.cloudflareinsights.com — assets: 1 · below probe threshold
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 38 ms lookup
PASS
2 A records, 38 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.8.159, 172.67.139.179
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3036::ac43:8bb3, 2606:4700:3032::6815:89f
Info::
2 nameserver(s) configured
Got: rocco.ns.cloudflare.com, elly.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A104.21.8.159, 172.67.139.179
AAAA2606:4700:3036::ac43:8bb3, 2606:4700:3032::6815:89f
CNAME—
NSrocco.ns.cloudflare.com, elly.ns.cloudflare.com
MX
10 smtp.google.com
TXT
SPF v=spf1 include:_spf.google.com include:amazonses.com ~all
google-site-verification=U-SCkceP0p37WZfyKZ8g4R7d1qC2lbn2xxJRu1su0Zo
google-site-verification=SLQUyKb6VgvAd8pL1yTc6HzWlZVWNYPEEHCn0G9txfg
CAALookup not available with standard resolver
Resolved in 38 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 37ms across 3 resolvers (spread 33ms)
PASS
Mean 37ms across 3 resolvers (spread 33ms)
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Google: 35ms
Got: 35ms via 8.8.8.8:53
Info::
Quad9: 55ms
Got: 55ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 334 ms total
PASS
1 redirect(s), 334 ms total
Info::
Single redirect
Got: https://peerpush.net → https://peerpush.com/ (301)
Info::
Cross-domain redirect detected

https://peerpush.net

71 ms · HTTP/1.1

301

https://peerpush.com/

263 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://peerpush.net30171 msHTTP/1.1cloudflare
2https://peerpush.com/200263 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3036::ac43:8bb3, 2606:4700:3032::6815:89f
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3036::ac43:8bb3, 2606:4700:3032::6815:89f Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 1208 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1208 B Sitemaps referenced 1 User-agents Google-Extended, FacebookBot, AhrefsBot, Applebot-Extended, CCBot, cohere-ai, SemrushBot, OAI-SearchBot, ClaudeBot, anthropic-ai, Bytespider, *, PerplexityBot, GPTBot, ChatGPT-User Blocking No — crawling allowed
User-agent: *
Content-Signal: ai-train=yes, search=yes, ai-input=yes
Allow: /
Disallow: /r/

# AI Search Engine Bots - Explicitly allowed (PeerPush is built to be
# found by AI; the Signals surface is intentionally crawlable). A named group
# replaces the * group for that crawler (RFC 9309), so it repeats the
# disallows. /auth/ is blocked only here: its pages are noindex, and Google
# must be able to crawl them to see that.
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Google-Extended
User-agent: PerplexityBot
User-agent: ClaudeBot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: Bytespider
User-agent: CCBot
User-agent: cohere-ai
User-agent: FacebookBot
Allow: /
Disallow: /r/
Disallow: /auth/

# SEO-tool crawlers - throttled (not blocked), purely for origin load:
# SemrushBot alone sent ~205k requests in 24h during the 2026-08-10 crawler
# wave that pushed the host into swap thrash. Crawl-delay keeps their index
# data flowing at ~1/10th the request rate.
User-agent: SemrushBot
Crawl-delay: 10
Disallow: /r/
Disallow: /auth/

User-agent: AhrefsBot
Crawl-delay: 10
Disallow: /r/
Disallow: /auth/

Sitemap: https://peerpush.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.peerpush.net/
200https://peerpush.net/

Preferred variant: non-www

HTTP → HTTPS

301http://peerpush.net/ → https://peerpush.com/

Consistent

A+
Domain Intelligence
peerpush.net — via Cloudflare, Inc., 1 years, 5 months old
PASS
peerpush.net — via Cloudflare, Inc., 1 years, 5 months old
Info::
Domain registered until May 24, 2027 (6 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Cloudflare, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

191 days

May 24, 2027

SSL certificate

84 days

Issued by Google Trust Services

Domain age

1 years, 5 months

Registered May 24, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3032::6815:89f

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created May 24, 2025 (1 years, 5 months ago)
Expires May 24, 2027 (6 months)
Last Updated April 24, 2026
Name Servers elly.ns.cloudflare.com, rocco.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3032::6815:89f
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 110 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
110 ms
Total Time Total request time from DNS lookup through full response.
110 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 32 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback