Infrastructure
· 16 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNS Records4 A records, 30 ms lookupREVIEW
| A | 198.185.159.144, 198.49.23.144, 198.49.23.145, 198.185.159.145 |
| AAAA | — |
| CNAME | ext-sq.squarespace.com |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
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'.
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)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS4 PTR record(s) found (no cert data to match against)REVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCDN & DeliveryDocument on Squarespace; assets also on FastlyREVIEW
Asset hosts on a CDN
- assets.squarespace.com — Fastly · assets: 13 · Cache Status: HIT, HIT
- images.squarespace-cdn.com — Fastly · assets: 12 · Cache Status: HIT, HIT
- static1.squarespace.com — Fastly · assets: 7 · Cache Status: HIT, HIT
Other asset hosts
- definitions.sqspcdn.com — assets: 26 · not attributed
- use.typekit.net — assets: 1 · below probe threshold
BOperational Status PageNo status page link detectedREVIEW
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 37ms across 3 resolvers (spread 37ms)PASS
ARedirect Chain1 redirect(s), 148 ms totalPASS
http://www.lindaschlapfer.com
58 ms · HTTP/1.1
https://www.lindaschlapfer.com/
89 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | http://www.lindaschlapfer.com | 301 | 58 ms | HTTP/1.1 | Squarespace |
| 2 | https://www.lindaschlapfer.com/ | 200 | 89 ms | HTTP/1.1 | Squarespace |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 17 URLsPASS
# 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.lindaschlapfer.com/sitemap.xml
- https://www.lindaschlapfer.com/about-linda
- https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/1597773126503-3CSZEEQYU7MZ433K1BGQ/G_002511_190129_crop%2B2.jpg
- https://www.lindaschlapfer.com/home
- https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/9d8ce406-2b73-41ba-9925-410e69d46624/Linda+Cube.png
- https://images.squarespace-cdn.com/content/v1/5f2af28e914d6a1c9f401002/1599591202767-L8EK5TD8VFLG38JV38WJ/7651027824_IMG_2946.JPG
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
A+Domain Intelligencelindaschlapfer.com — via GoDaddy.com, LLC, 17 years, 9 months old, hosted on SquarespacePASS
545 days
April 1, 2028
No certificate data
17 years, 9 months
Registered April 1, 2009
Not enabled
Protects against DNS spoofing
Squarespace
ASN AS53831
198.185.159.144
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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