Skip to content
https://zachbloss.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from New York, United Stated
200 OK
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.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 18.173.219.14 does not match any cert SAN: server-18-173-219-14.jfk52.r.cloudfront.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 18.173.219.90 does not match any cert SAN: server-18-173-219-90.jfk52.r.cloudfront.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 18.173.219.75 does not match any cert SAN: server-18-173-219-75.jfk52.r.cloudfront.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 18.173.219.97 does not match any cert SAN: server-18-173-219-97.jfk52.r.cloudfront.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.
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.zachbloss.com/
200https://zachbloss.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

140
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
AWS CloudFront (Error from cloudfront)
REVIEW
AWS CloudFront (Error from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: JFK52-P1)
Got: x-amz-cf-id: rB2WhzoIN10Io-Z3d0Q-sdXjPWUL16mIXRie3OWV95dSogWmzeV4cA==
Info::
CDN cache status: Error from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Error from cloudfront Evidence x-amz-cf-id: rB2WhzoIN10Io-Z3d0Q-sdXjPWUL16mIXRie3OWV95dSogWmzeV4cA==
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
4 A records, 13 ms lookup
PASS
4 A records, 13 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.173.219.14, 18.173.219.90, 18.173.219.75, 18.173.219.97
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1449.awsdns-53.org, ns-1699.awsdns-20.co.uk, ns-31.awsdns-03.com, ns-774.awsdns-32.net
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: 13 ms
Got: 13 ms
A18.173.219.14, 18.173.219.90, 18.173.219.75, 18.173.219.97
AAAA—
CNAME—
NSns-1449.awsdns-53.org, ns-1699.awsdns-20.co.uk, ns-31.awsdns-03.com, ns-774.awsdns-32.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 13 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 11ms across 3 resolvers (spread 13ms)
PASS
Mean 11ms across 3 resolvers (spread 13ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
Info::
Quad9: 16ms
Got: 16ms 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://zachbloss.com

https://zachbloss.com

154 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://zachbloss.com200154 msHTTP/1.1AmazonS3
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 69 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 69 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /


Sitemap: https://zachbloss.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 2 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
zachbloss.com — via Amazon Registrar, Inc., 10 years, 2 months old, hosted on AWS
PASS
zachbloss.com — via Amazon Registrar, Inc., 10 years, 2 months old, hosted on AWS
Info::
Domain registered until Apr 15, 2027 (11 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: Amazon Registrar, 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

335 days

April 15, 2027

SSL certificate

140 days

Issued by Amazon

Domain age

10 years, 2 months

Registered April 15, 2016

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.173.219.90

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created April 15, 2016 (10 years, 2 months ago)
Expires April 15, 2027 (11 months)
Last Updated March 11, 2026
Name Servers ns-1449.awsdns-53.org, ns-1699.awsdns-20.co.uk, ns-31.awsdns-03.com, ns-774.awsdns-32.net
DNSSEC Not enabled
Hosting
IP Address 18.173.219.90
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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 269 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
15 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.
11 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
270 ms
Total Time Total request time from DNS lookup through full response.
270 ms

Connection waterfall

DNS Lookup 15 ms TCP Connect 1 ms TLS Handshake 11 ms Server Processing 242 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: ERROR
PASS
Cache state: ERROR
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Error from cloudfront
A+
Health Check Endpoint
Health endpoint at https://zachbloss.com/health (HTTP 200)
PASS
Health endpoint at https://zachbloss.com/health (HTTP 200)
Info::
Public health endpoint at https://zachbloss.com/health
Got: https://zachbloss.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