Skip to content
https://petesrestaurants.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 7 REVIEW 1 FIX
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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 198.185.159.145: lookup 198.185.159.145: 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 198.49.23.145: lookup 198.49.23.145: 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 198.185.159.144: lookup 198.185.159.144: 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 198.49.23.144: lookup 198.49.23.144: 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
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.petesrestaurants.com/
200https://petesrestaurants.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://petesrestaurants.com/ → https://www.petesrestaurants.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
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, 34 ms lookup
PASS
4 A records, 34 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 198.185.159.145, 198.49.23.145, 198.185.159.144, 198.49.23.144
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns03.squarespacedns.com, dns1.p08.nsone.net, ns04.squarespacedns.com, dns2.p08.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, dns4.p08.nsone.net, dns3.p08.nsone.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 34 ms
Got: 34 ms
A198.185.159.145, 198.49.23.145, 198.185.159.144, 198.49.23.144
AAAA—
CNAME—
NSns03.squarespacedns.com, dns1.p08.nsone.net, ns04.squarespacedns.com, dns2.p08.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, dns4.p08.nsone.net, dns3.p08.nsone.net
MX
10 mx.petesrestaurants.com
TXT
SPF v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ip4:65.254.224.0/19 ?all
CAALookup not available with standard resolver
Resolved in 34 ms
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 20ms across 3 resolvers (spread 38ms)
PASS
Mean 20ms across 3 resolvers (spread 38ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 39ms
Got: 39ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 517 ms total
PASS
1 redirect(s), 517 ms total
Info::
Single redirect
Got: https://petesrestaurants.com → https://www.petesrestaurants.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 517 ms total
Got: 517 ms

https://petesrestaurants.com

128 ms · HTTP/1.1

301

https://www.petesrestaurants.com/

390 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://petesrestaurants.com301128 msHTTP/1.1Squarespace
2https://www.petesrestaurants.com/200390 msHTTP/1.1Squarespace

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 1515 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1515 B Sitemaps referenced 1 User-agents ClaudeBot, cohere-training-data-crawler, Google-Extended, Quora-Bot, AdsBot-Google, aiHitBot, cohere-ai, DuckAssistBot, GoogleOther-Video, Meta-ExternalAgent, GoogleOther-Image, img2dataset, AdsBot-Google-Mobile-Apps, MyCentralAIScraperBot, AdsBot-Google-Mobile, Amazonbot, anthropic-ai, omgili, *, AI2Bot, Applebot-Extended, TikTokSpider, YouBot, Ai2Bot-Dolma, Bytespider, CCBot, FacebookBot, GoogleOther, GPTBot, omgilibot Blocking No — crawling allowed
# Squarespace Robots Txt

User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: Amazonbot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: Bytespider
User-agent: CCBot
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: img2dataset
User-agent: Meta-ExternalAgent
User-agent: MyCentralAIScraperBot
User-agent: omgili
User-agent: omgilibot
User-agent: Quora-Bot
User-agent: TikTokSpider
User-agent: YouBot
User-agent: AdsBot-Google
User-agent: AdsBot-Google-Mobile
User-agent: AdsBot-Google-Mobile-Apps
User-agent: *
Disallow: /config
Disallow: /search
Disallow: /account$
Disallow: /account/
Disallow: /commerce/digital-download/
Disallow: /api/
Allow: /api/ui-extensions/
Disallow: /static/
Disallow:/*?author=*
Disallow:/*&author=*
Disallow:/*?tag=*
Disallow:/*&tag=*
Disallow:/*?month=*
Disallow:/*&month=*
Disallow:/*?view=*
Disallow:/*&view=*
Disallow:/*?format=json
Disallow:/*&format=json
Disallow:/*?format=page-context
Disallow:/*&format=page-context
Disallow:/*?format=main-content
Disallow:/*&format=main-content
Disallow:/*?format=json-pretty
Disallow:/*&format=json-pretty
Disallow:/*?format=ical
Disallow:/*&format=ical
Disallow:/*?reversePaginate=*
Disallow:/*&reversePaginate=*

Sitemap: https://www.petesrestaurants.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 13 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
petesrestaurants.com — via Tucows Domains Inc., 24 years, 1 months old, hosted on Squarespace
PASS
petesrestaurants.com — via Tucows Domains Inc., 24 years, 1 months old, hosted on Squarespace
Warning::
Domain expires in 74 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 24, 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: Tucows Domains 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: Squarespace
Got: AS53831
Domain expiry

70 days

July 24, 2026

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

24 years, 1 months

Registered July 24, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Squarespace

ASN AS53831

198.49.23.145

Registrar

Tucows Domains Inc.

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created July 24, 2002 (24 years, 1 months ago)
Expires July 24, 2026 (2 months)
Last Updated February 1, 2026
Name Servers dns1.p08.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com
DNSSEC Not enabled
Hosting
IP Address 198.49.23.145
ASN AS53831 (SQUARESPACE - Squarespace, Inc., US)
Provider Squarespace
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 385 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
114 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
116 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
386 ms
Total Time Total request time from DNS lookup through full response.
386 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 114 ms TLS Handshake 116 ms Server Processing 118 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: Age=133540s
PASS
Cache state: Age=133540s
Info::
CDN cache state observable via 1 header(s)
Got: age=133540
A+
Health Check Endpoint
Health endpoint at https://petesrestaurants.com/healthz (HTTP 200)
PASS
Health endpoint at https://petesrestaurants.com/healthz (HTTP 200)
Info::
Public health endpoint at https://petesrestaurants.com/healthz
Got: https://petesrestaurants.com/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback