Skip to content
https://www.creativeandbeyondph.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
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
DNS Records
4 A records, 29 ms lookup
REVIEW
4 A records, 29 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 198.185.159.144, 198.185.159.145, 198.49.23.145, 198.49.23.144
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: ext-sq.squarespace.com
Info::
No NS records found
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: 29 ms
Got: 29 ms
A198.185.159.144, 198.185.159.145, 198.49.23.145, 198.49.23.144
AAAA
CNAMEext-sq.squarespace.com
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 29 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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.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.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.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
TLS Certificate Expiry & Recommendations
71 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

71
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 39ms across 3 resolvers (spread 19ms)
PASS
Mean 39ms across 3 resolvers (spread 19ms)
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
Info::
Quad9: 45ms
Got: 45ms via 9.9.9.9:53
Info::
Cloudflare: 46ms
Got: 46ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.creativeandbeyondph.com

https://www.creativeandbeyondph.com

104 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.creativeandbeyondph.com200104 msHTTP/1.1Squarespace
A+
Crawlability
robots.txt present, sitemap with 101 URLs
PASS
robots.txt present, sitemap with 101 URLs
Info::
robots.txt is present
Got: 1518 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 101 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1518 B Sitemaps referenced 1 User-agents cohere-ai, Quora-Bot, Amazonbot, anthropic-ai, FacebookBot, AdsBot-Google-Mobile-Apps, AI2Bot, Ai2Bot-Dolma, Google-Extended, GoogleOther-Image, YouBot, AdsBot-Google-Mobile, GoogleOther-Video, img2dataset, MyCentralAIScraperBot, AdsBot-Google, omgili, omgilibot, aiHitBot, Bytespider, CCBot, ClaudeBot, GPTBot, Applebot-Extended, DuckAssistBot, GoogleOther, TikTokSpider, cohere-training-data-crawler, Meta-ExternalAgent, * 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.creativeandbeyondph.com/sitemap.xml

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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.creativeandbeyondph.com/ https://www.creativeandbeyondph.com/

Consistent

A+
Domain Intelligence
creativeandbeyondph.com — via Tucows Domains Inc., 8 years, 2 months old, hosted on Squarespace
PASS
creativeandbeyondph.com — via Tucows Domains Inc., 8 years, 2 months old, hosted on Squarespace
Info::
Domain registered until Apr 18, 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: 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

338 days

April 18, 2027

SSL certificate

71 days

Issued by Let's Encrypt

Domain age

8 years, 2 months

Registered April 18, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Squarespace

ASN AS53831

198.49.23.144

Registrar

Tucows Domains Inc.

Unlocked 8 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 Tucows Domains Inc.
Created April 18, 2018 (8 years, 2 months ago)
Expires April 18, 2027 (11 months)
Last Updated April 3, 2026
Name Servers dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com
DNSSEC Not enabled
Hosting
IP Address 198.49.23.144
ASN AS53831 (SQUARESPACE - Squarespace, Inc., US)
Provider Squarespace
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 631 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
58 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
111 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
119 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
407 ms
Total Time Total request time from DNS lookup through full response.
632 ms

Connection waterfall

DNS Lookup 58 ms TCP Connect 111 ms TLS Handshake 119 ms Server Processing 118 ms Content Transfer 224 ms
A+
CDN Cache Observability
Cache state: Age=114962s
PASS
Cache state: Age=114962s
Info::
CDN cache state observable via 1 header(s)
Got: age=114962
A+
Health Check Endpoint
Health endpoint at https://www.creativeandbeyondph.com/healthz (HTTP 200)
PASS
Health endpoint at https://www.creativeandbeyondph.com/healthz (HTTP 200)
Info::
Public health endpoint at https://www.creativeandbeyondph.com/healthz
Got: https://www.creativeandbeyondph.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