reverselookup.com

Readiness by lane

Green: reverselookup.com. Thin bar: Web Tools peer median.

Priority fixes for reverselookup.com

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

1. Priority 1 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 6 images and none used loading="lazy".

   Why it matters: Images below the fold are only downloaded when the visitor scrolls near them, which frees bandwidth for what is visible first.

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   59% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Lazy Loading Without Broken Pages

2. Priority 2 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   15% of Web Tools peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for reverselookup.com, 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.

   14% of Web Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   DNSSEC signed

   Observed: No DS record was found for reverselookup.com at its parent zone, so its DNS answers are not DNSSEC-signed.

   What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

   On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

   9.3% of Web Tools peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What reverselookup.com already does well

Practices fewer than half of Web Tools peers use.

• security.txt publishedsecurity.txt with a contact found.4.8% of peers
• Nameservers spread across providersNameservers spread across more than one operator.6.1% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers

What we saw

Homepage checked

https://reverselookup.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-12

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

574 KB, gzip

Images on homepage

6 (png 4, webp 1, svg 1)

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 Web Tools sites

• claritycheck.com88
• firefox.com90
• grizzlysms.com91
• ingles.com91
• notube.lol87

Web Tools readiness benchmark