Skip to content
https://lalignenyc.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 10 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 23.227.38.65 does not match any cert SAN: myshopify.com
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
Multi-Resolver DNS Speed
Mean 45ms across 3 resolvers (spread 108ms)
REVIEW
Mean 45ms across 3 resolvers (spread 108ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
Info::
Google: 109ms
Got: 109ms via 8.8.8.8:53
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
84 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

84
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 & Delivery
Document on Cloudflare; assets also on Fastly
REVIEW
Document on Cloudflare; assets also on Fastly
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a52cf3f9283dd09e-CDG
Info::
Assets on Cloudflare: cdn.shopify.com (assets: 51), cache HIT
Got: cf-ray: a52cf57a9b3902dd-CDG
Info::
Assets on Fastly: static.klaviyo.com (assets: 14), cache HIT, HIT
Got: delegation klaviyo-onsite.map.fastly.net
Info::
Assets on Fastly: static-tracking.klaviyo.com (assets: 4), cache HIT, HIT
Got: delegation klaviyo-app.map.fastly.net
Info::
Assets on Cloudflare: dsrp-platform.pii.ai (assets: 3), cache DYNAMIC
Got: cf-ray: a52cf57a9ca4c184-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a52cf3f9283dd09e-CDG

Asset hosts on a CDN

  • cdn.shopify.com — Cloudflare · assets: 51 · Cache Status: HIT
  • static.klaviyo.com — Fastly · assets: 14 · Cache Status: HIT, HIT
  • static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT
  • dsrp-platform.pii.ai — Cloudflare · assets: 3 · Cache Status: DYNAMIC

Other asset hosts

  • cdn.cookie.pii.ai — assets: 2 · below probe threshold
  • dashboard.heatmap.com — assets: 2 · below probe threshold
  • j.northbeam.io — assets: 2 · below probe threshold
  • tdpfe.lalignenyc.com — assets: 2 · below probe threshold
  • backend.alia-prod.com — assets: 1 · below probe threshold
  • cdn.attn.tv — assets: 1 · below probe threshold
  • static.shopmy.us — assets: 1 · below probe threshold
  • www.googletagmanager.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
1 A records, 28 ms lookup
PASS
1 A records, 28 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.227.38.65
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns13.domaincontrol.com, ns14.domaincontrol.com
Info::
7 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 28 ms
Got: 28 ms
A23.227.38.65
AAAA—
CNAME—
NSns13.domaincontrol.com, ns14.domaincontrol.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 mxb.mailgun.org
10 aspmx3.googlemail.com
10 mxa.mailgun.org
TXT
google-site-verification=duMCSFI1I9nTO6RETT2tttW4py_04oTwTyFNRFD0V9Q
google-site-verification=W0dxDckWBCYS3GsdiZHacnogTiPEAtDzMU8tq9RHjbY
google-site-verification=DSP--exrlW0WbNkoHuFHFoXm94a0ZK-njmb7hij4oVs
facebook-domain-verification=scgssbn01kki3l4tryqw8xaw4fh9ou
google-gws-recovery-domain-verification=77064768
google-gws-recovery-domain-verification=77065359
google-site-verification=uMHlYXzP63cKguUTL8zaKQw5jF-9IzXR3gqfpZuCyOg
SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:mailgun.org ~...
klaviyo-site-verification=PPGGLG
pinterest-site-verification=7b8da8b6a59eebe8e89e47c62010281d
google-site-verification=0sYt7V9nwkDTLDTWGu47IMINcpQJht321tGD5aw5wZ0
anthropic-domain-verification-qkrxth=fjAgLrQ28rlAGE3H6dJpynZDy
uber-domain-verification=af1ede1f-57b6-4ac8-b33b-f3e408a2c545
CAALookup not available with standard resolver
Resolved in 28 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://lalignenyc.com

https://lalignenyc.com

252 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lalignenyc.com200252 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 1621 URLs
PASS
robots.txt present, sitemap with 1621 URLs
Info::
robots.txt is present
Got: 1736 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1621 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1736 B Sitemaps referenced 1 User-agents *, adsbot-google, AhrefsBot, AhrefsSiteAudit, Nutch, MJ12bot, Pinterest, Googlebot, Googlebot-image Blocking No — crawling allowed
User-agent: *
    Disallow: /admin
    Disallow: /cart
    Disallow: /orders
    Disallow: /checkouts/
    Disallow: /checkout
    Disallow: /carts
    Disallow: /account
    Disallow: /collections/*sort_by*
    Disallow: /*/collections/*sort_by*
    Disallow: /collections/*+*
    Disallow: /collections/*%2B*
    Disallow: /collections/*%2b*
    Disallow: /*/collections/*+*
    Disallow: /*/collections/*%2B*
    Disallow: /*/collections/*%2b*
    Disallow: */collections/*filter*&*filter*
    Disallow: /blogs/*+*
    Disallow: /blogs/*%2B*
    Disallow: /blogs/*%2b*
    Disallow: /*/blogs/*+*
    Disallow: /*/blogs/*%2B*
    Disallow: /*/blogs/*%2b*
    Disallow: /*?*oseid=*
    Disallow: /*preview_theme_id*
    Disallow: /*preview_script_id*
    Disallow: /policies/
    Disallow: /*/policies/
    Disallow: /*/*?*ls=*&ls=*
    Disallow: /*/*?*ls%3D*%3Fls%3D*
    Disallow: /*/*?*ls%3d*%3fls%3d*
    Disallow: /search
    Disallow: /apple-app-site-association
    Disallow: /.well-known/shopify/monorail
    Disallow: /cdn/wpm/*.js
    Disallow: /recommendations/products
    Disallow: /*/recommendations/products
    Disallow: /*?Size*
    Disallow: /*?direction=next*

    Sitemap: https://lalignenyc.com/sitemap.xml

    # Google adsbot ignores robots.txt unless specifically named!
    User-agent: adsbot-google
    Disallow: /checkouts/
    Disallow: /checkout
    Disallow: /carts
    Disallow: /orders

    User-agent: Nutch
    Disallow: /

    User-agent: AhrefsBot
    Crawl-delay: 10

    User-agent: AhrefsSiteAudit
    Crawl-delay: 10

    User-agent: MJ12bot
    Crawl-delay: 10

    User-agent: Pinterest
    Crawl-delay: 1

    User-agent: Googlebot
    Disallow:

    User-agent: Googlebot-image
    Disallow:
sitemap.xml 200 OK
Type URL Set URLs 1621 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::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

429https://www.lalignenyc.com/
200https://lalignenyc.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
lalignenyc.com — via GoDaddy.com, LLC, 12 years, 4 months old, hosted on Cloudflare
PASS
lalignenyc.com — via GoDaddy.com, LLC, 12 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until Aug 8, 2028 (1 years, 9 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: GoDaddy.com, LLC
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: Cloudflare
Got: AS13335
Domain expiry

639 days

August 8, 2028

SSL certificate

84 days

Issued by Let's Encrypt

Domain age

12 years, 4 months

Registered August 8, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.65

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created August 8, 2014 (12 years, 4 months ago)
Expires August 8, 2028 (1 years, 9 months)
Last Updated October 30, 2026
Name Servers ns13.domaincontrol.com, ns14.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 23.227.38.65
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 177 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 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.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
164 ms
Total Time Total request time from DNS lookup through full response.
178 ms

Connection waterfall

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

Send Feedback