Skip to content
https://manuelmedina.me

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 199.16.172.115: lookup 199.16.172.115: 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 199.16.173.184: lookup 199.16.173.184: 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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
71 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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.
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: 429, /health: 429, /healthz: 429, /ping: 429, /status: 429.
A+
DNS Records
2 A records, 24 ms lookup
PASS
2 A records, 24 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 199.16.172.115, 199.16.173.184
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns5.openhostingservice.com, ns3.openhostingservice.com, ns1.openhostingservice.com, ns4.openhostingservice.com, ns2.openhostingservice.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A199.16.172.115, 199.16.173.184
AAAA—
CNAME—
NSns5.openhostingservice.com, ns3.openhostingservice.com, ns1.openhostingservice.com, ns4.openhostingservice.com, ns2.openhostingservice.com
MX—
TXT
atomic-domain-19379252cd258d12c00498f2b14cdf28d3c5e5a77d2fbdcbb81ac284e5f78202
google-site-verification=yiBCrVEZKWOpUd8Iem3qJVe1KUJperOiI4pXeKTA2g8
CAALookup not available with standard resolver
Resolved in 24 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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 4ms across 3 resolvers (spread 4ms)
PASS
Mean 4ms across 3 resolvers (spread 4ms)
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Quad9: 4ms
Got: 4ms via 9.9.9.9:53
Info::
Google: 6ms
Got: 6ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://manuelmedina.me

https://manuelmedina.me

170 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://manuelmedina.me200170 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 161 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 161 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
Sitemap: https://manuelmedina.me/sitemap.xml
Sitemap: https://manuelmedina.me/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
sitemap.xml 200 OK
Type Sitemap Index URLs 2 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.manuelmedina.me/
200https://manuelmedina.me/

Preferred variant: non-www

HTTP → HTTPS

301http://manuelmedina.me/ → https://manuelmedina.me/

Consistent

A+
Domain Intelligence
manuelmedina.me — via Automattic Inc., 10 years, 1 months old, hosted on WordPress.com (Automattic)
PASS
manuelmedina.me — via Automattic Inc., 10 years, 1 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Oct 3, 2027 (1 years remaining)
Info::
Registrar: Automattic Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

363 days

October 3, 2027

SSL certificate

71 days

Issued by Google Trust Services

Domain age

10 years, 1 months

Registered October 3, 2016

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

199.16.172.115

Registrar

Automattic Inc.

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Automattic Inc.
Created October 3, 2016 (10 years, 1 months ago)
Expires October 3, 2027 (1 years)
Last Updated September 20, 2026
Name Servers ns1.openhostingservice.com, ns2.openhostingservice.com, ns3.openhostingservice.com, ns4.openhostingservice.com
Registrant Knock Knock WHOIS Not There, LLC
Hosting
IP Address 199.16.172.115
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: whois (1.4s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 121 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 201 ms Content Transfer 42 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback