Skip to content
https://potentialspouse.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
2
REVIEW
6
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 6 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 9834 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
33 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
142 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
9.83 s
Total Time Total request time from DNS lookup through full response.
9.83 s

Connection waterfall

DNS Lookup 33 ms TCP Connect 25 ms TLS Handshake 142 ms Server Processing 9.63 s Content Transfer 2 ms
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 66.241.125.149 does not match any cert SAN: ip-66-241-125-149.shared.customer.flyio.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a09:8280:1::112:4174:0 does not match any cert SAN: ipv6.customer.flyio.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
TLS Certificate Expiry & Recommendations
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 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.
A+
DNS Records
1 A records, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 66.241.125.149
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a09:8280:1::112:4174:0
Info::
2 nameserver(s) configured
Got: dns2.registrar-servers.com, dns1.registrar-servers.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A66.241.125.149
AAAA2a09:8280:1::112:4174:0
CNAME—
NSdns2.registrar-servers.com, dns1.registrar-servers.com
MX
10 eforward2.registrar-servers.com
10 eforward1.registrar-servers.com
10 eforward3.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
CAALookup not available with standard resolver
Resolved in 36 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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 39ms across 3 resolvers (spread 48ms)
PASS
Mean 39ms across 3 resolvers (spread 48ms)
Info::
Cloudflare: 23ms
Got: 23ms via 1.1.1.1:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
Info::
Quad9: 71ms
Got: 71ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://potentialspouse.com

https://potentialspouse.com

96 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://potentialspouse.com20096 msHTTP/1.1Fly/a589ac11 (2026-05-08)
A+
IPv6 Readiness
IPv6 reachable (24 ms)
PASS
IPv6 reachable (24 ms)
Info::
IPv6 is configured and reachable at 2a09:8280:1::112:4174:0
Got: 24 ms connect
IPv6 Ready
AAAA Records 2a09:8280:1::112:4174:0 Connection Reachable (24 ms)
A+
Crawlability
robots.txt present, sitemap with 15 URLs
PASS
robots.txt present, sitemap with 15 URLs
Info::
robots.txt is present
Got: 1388 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 15 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1388 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# PotentialSpouse is a private matchmaking application — profile
# data, codenames, chat content, and any signed-in route MUST NOT be
# indexed by search engines. The public marketing surface (homepage,
# /about, /use-cases, /support, /terms, /privacy, /blog) is fair game
# and helps people find the product when they have a real need; the
# rest is denied.
#
# See `project/PRD.md` §3 and `project/reveal_ladder.md` for the
# anti-recognition posture these rules reinforce.

User-agent: *

# Authenticated app surface — never indexable.
Disallow: /wall
Disallow: /notifications
Disallow: /connections
Disallow: /connections/
Disallow: /profile
Disallow: /profile/
Disallow: /settings
Disallow: /settings/
Disallow: /report
Disallow: /admin
Disallow: /admin/

# Auth + onboarding surfaces — also denied so a returning user's
# codename never appears in a search snippet via cached state.
Disallow: /users/
Disallow: /auth/
Disallow: /onboarding/

# Operational endpoints.
Disallow: /api/
Disallow: /health
Disallow: /readiness
Disallow: /dev/

# Everything else (homepage + public marketing pages + blog) is
# allowed by default — Allow lines exist so robots that read both
# rules pick the most permissive match.
Allow: /
Allow: /about
Allow: /use-cases
Allow: /support
Allow: /terms
Allow: /privacy
Allow: /blog
Allow: /blog/

Sitemap: https://potentialspouse.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 15 entries Valid XML Yes
Sample URLs:
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 301-redirects to HTTPS

www / non-www

301https://www.potentialspouse.com/
200https://potentialspouse.com/

Preferred variant: non-www

HTTP → HTTPS

301http://potentialspouse.com/ → https://potentialspouse.com/

Consistent

A+
Domain Intelligence
potentialspouse.com — via NameCheap, Inc., 2 days old
PASS
potentialspouse.com — via NameCheap, Inc., 2 days old
Info::
Domain registered until May 7, 2027 (1 years remaining)
Info::
Domain is only 2 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered May 7, 2026
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: NameCheap, 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

357 days

May 7, 2027

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

2 days

Registered May 7, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a09:8280:1::112:4174:0

Registrar

NameCheap, 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created May 7, 2026 (2 days ago)
Expires May 7, 2027 (1 years)
Last Updated May 7, 2026
Name Servers dns1.registrar-servers.com, dns2.registrar-servers.com
DNSSEC Not enabled
Hosting
IP Address 2a09:8280:1::112:4174:0
Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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+
Health Check Endpoint
Health endpoint at https://potentialspouse.com/health (HTTP 200)
PASS
Health endpoint at https://potentialspouse.com/health (HTTP 200)
Info::
Public health endpoint at https://potentialspouse.com/health
Got: https://potentialspouse.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback