Skip to content
https://laist.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 3 REVIEW
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
HTTP Probe Timing
Total 1438 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.30 s
Total Time Total request time from DNS lookup through full response.
1.44 s

Connection waterfall

DNS Lookup 40 ms TCP Connect 16 ms TLS Handshake 18 ms Server Processing 1.23 s Content Transfer 138 ms
B
TLS Certificate Expiry & Recommendations
295 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

295
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
A+
DNS Records
4 A records, 45 ms lookup
PASS
4 A records, 45 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.245.175.64, 18.245.175.17, 18.245.175.109, 18.245.175.119
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-635.awsdns-15.net, ns-118.awsdns-14.com, ns-1852.awsdns-39.co.uk, ns-1144.awsdns-15.org
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A18.245.175.64, 18.245.175.17, 18.245.175.109, 18.245.175.119
AAAA—
CNAME—
NSns-635.awsdns-15.net, ns-118.awsdns-14.com, ns-1852.awsdns-39.co.uk, ns-1144.awsdns-15.org
MX
0 laist-com.mail.protection.outlook.com
TXT
SPF v=spf1 ip4:192.203.201.30 include:spf.protection.outlook.com include:_spf.salesf...
MS=ms24427093
airtable-verification=033ca0273c484f7d261427c5ae412535
ZOOM_verify_AhXaQEaOha6IjsshIIfvWB
google-site-verification=rBlTNSntE8ZiYqgv6BrDmg8RnvHKd41wWgvSOtZkDf0
google-site-verification=sxXBszKjlseoiecBFG0sGloWVnQtQa26H2fYvqZ4t8o
google-site-verification=sY-mYf2p-hkEy35Kyn-1R1IBRj2-JJpdyZGrzDSngwE
CAALookup not available with standard resolver
Resolved in 45 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://laist.com

https://laist.com

55 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://laist.com20055 msHTTP/1.1istio-envoy
A+
Crawlability
robots.txt present, sitemap with 267 URLs
PASS
robots.txt present, sitemap with 267 URLs
Info::
robots.txt is present
Got: 555 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 267 entries
Info::
Sitemap index with 267 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 555 B Sitemaps referenced 3 User-agents CCBot, bingbot, GPTBot, ChatGPT-User Blocking No — crawling allowed
# Block ChatGPT
# More info: https://platform.openai.com/docs/gptbot
User-agent: GPTBot
Disallow: /

# Block ChatGPT plug-in
# More info: https://platform.openai.com/docs/plugins/bot
User-agent: ChatGPT-User
Disallow: /

# Block Common Crawl (CCBot)
# More info: https://commoncrawl.org/faq
User-agent: CCBot
Disallow: /

# Block Bingbot from repeatedly querying search function
User-agent: bingbot
Disallow: /search

Sitemap: https://laist.com/sitemap.xml
Sitemap: https://laist.com/sitemap-latest.xml
Sitemap: https://laist.com/news-sitemap-content.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 267 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 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
laist.com — via Amazon Registrar, Inc., 22 years, 5 months old, hosted on AWS
PASS
laist.com — via Amazon Registrar, Inc., 22 years, 5 months old, hosted on AWS
Info::
Domain registered until Mar 18, 2027 (10 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

276 days

March 18, 2027

SSL certificate

295 days

Issued by Amazon

Domain age

22 years, 5 months

Registered March 18, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.245.175.17

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 March 18, 2004 (22 years, 5 months ago)
Expires March 18, 2027 (10 months)
Last Updated February 11, 2026
Name Servers ns-1144.awsdns-15.org, ns-118.awsdns-14.com, ns-1852.awsdns-39.co.uk, ns-635.awsdns-15.net
DNSSEC Not enabled
Hosting
IP Address 18.245.175.17
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG55-P1)
Got: x-amz-cf-id: 39tvsXVGzNauoeISHnDpgGwR34sEEToHMGDVpEMAOWIC2ZgO37m1jQ==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: 39tvsXVGzNauoeISHnDpgGwR34sEEToHMGDVpEMAOWIC2ZgO37m1jQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback