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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United Stated
301 Moved Permanently
Checks
9
4 PASS 4 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
8 A records, 203 ms lookup
REVIEW
8 A records, 203 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 3.213.173.32, 52.22.128.3, 100.24.232.72, 44.220.220.8, 3.223.224.218, 54.211.161.233, 54.227.218.56, 44.216.98.232
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: webflow.com
Info::
4 nameserver(s) configured
Got: ns-1078.awsdns-06.org, ns-1722.awsdns-23.co.uk, ns-344.awsdns-43.com, ns-958.awsdns-55.net
Info::
5 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
Warning::
DNS resolution is slow (203 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 203 ms
A3.213.173.32, 52.22.128.3, 100.24.232.72, 44.220.220.8, 3.223.224.218, 54.211.161.233, 54.227.218.56, 44.216.98.232
AAAA
CNAMEwebflow.com
NSns-1078.awsdns-06.org, ns-1722.awsdns-23.co.uk, ns-344.awsdns-43.com, ns-958.awsdns-55.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
a--ZbWEx22eC1OzXyIYkzUHxyCa30U4
apple-domain-verification=JyJNP680tZLN6J8E
asv=8c460543decb140b87537caf58b0eed9
atlassian-domain-verification=vyA0bNKYZHNbZ9LbbOu8Aa28WajPCCJ53qO9/idxMUDkdOdta9...
atlassian-sending-domain-verification=b3059a1a-7d62-4ed9-8cb7-19a228943ed2
docker-verification=f6eb7150-2c4d-42e3-a1d5-a71ed7b41947
docusign=8205d05f-50c2-4f88-b454-f5ced0363215
drift-domain-verification=bec89e0da98bf36f6e5c3d99bddaf800d78f7c6a697112bd1a1616...
dropbox-domain-verification=hhwd9eo2aak2
facebook-domain-verification=wim5aiikqmubjhpgjlea0grlcy4arz
fireflies-verification=01KM0TS4HANF93ACVSS0G2CSKX.ffverify.fireflies.ai-request-...
gc-ai-domain-verification-0k0qqg=5zGKAndwdUGAEEyCKjPKn5nnU
gentrace-domain-verification=9ea62305-a906-4c5d-9c5a-2f5feb37f859
google-site-verification=3xpiScIbxMGgY_V5bYXY3JDJORGlv5nmA2tQmE5QxSk
hubspot-developer-verification=NWRmZjRhNmYtNzAzNi00MDZkLTgyODgtZWMzMjIzZTUwYzJi
jamf-site-verification=dkoLzLTQPiBnSg2osl_ItQ
loom-site-verification=f10b939df67b4d06a42dadb2c7b3ff43
mgverify=2eb750df10b6c31a1e3ef27a0d06844b676644792b4ea6ea08715cb137dfb1bd
miro-verification=c52af6e00d431e8c515bc6889548fefc20cd888e
mongodb-site-verification=nAdRq1BV7wGB1U3IAgrrJlUD2vAPZQHQ
onetrust-domain-verification=cf4f0c9e0a544dcf8c4d5077ad4cd03e
openai-domain-verification=dv-5HdMPAlHXfCAoIOEkUTaVhGz
postman-domain-verification=f6a7d2f52435f16105a25c66f173054e9db7d2e4e7bacf4fda44...
ps-cd-verification=f20b97a8-228d-424e-8bfe-131ed5598c37
reachdesk-verification=EXkA6I7Em5MHAKi4IsBuS2Wx2EOSbwxPDYyVaYBL2IJY6cOgcz2oFoEXf...
remote-domain-verification=c86c15b2-88e3-470c-963c-c2ba01190ed6
segment-site-verification=s002M3sGMlRXc1kaK40eXaRqerGhLlpZ
stripe-verification=081188df8f2b18461958e266de4b6e0c3a5c51f3d4c570653675af0c5505...
stripe-verification=4a619994910710fc7d530a0db04a8dd60ff6e79a9f72f97e28177a2f3295...
v=MCPv1; k=ed25519; p=TryMv95qd4OZPnc6IWmQ3BC7cD8Gcwb3urt3EzAFZ3E=
v=STSv1;id=1750164986635;
v=TLSRPTv1;rua=mailto:smtp-tls-reports@webflow.com;
SPF v=spf1 include:_spf.google.com include:spf.mailjet.com include:mail.zendesk.com ...
CAALookup not available with standard resolver
Resolved in 203 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

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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.webflow.com/
200https://webflow.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.webflow.com/ https://www.webflow.com:443/

Consistent

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

Certificate validity

200
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
A
Redirect Chain
1 redirect(s), 509 ms total
PASS
1 redirect(s), 509 ms total
Info::
Single redirect
Got: https://www.webflow.com → https://webflow.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 509 ms total
Got: 509 ms

https://www.webflow.com

249 ms · HTTP/1.1

301

https://webflow.com/

260 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.webflow.com301249 msHTTP/1.1
2https://webflow.com/200260 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 223 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 223 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /admin/
Disallow: /template/
Disallow: /design/
Disallow: /dashboard/
Allow: /api/discover/sites/
Allow: /api/v1/marketplace/made-in-webflow/
Disallow: /api/
Sitemap: https://webflow.com/sitemap.xml

A+
Domain Intelligence
webflow.com — via MarkMonitor Inc., 23 years, 4 months old, hosted on AWS
PASS
webflow.com — via MarkMonitor Inc., 23 years, 4 months old, hosted on AWS
Info::
Domain registered until May 9, 2029 (3 years, 1 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: MarkMonitor Inc.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

1058 days

May 9, 2029

SSL certificate

200 days

Issued by Amazon

Domain age

23 years, 4 months

Registered March 31, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.22.128.3

Registrar

MarkMonitor Inc.

Lock status unknown 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
Registrar MarkMonitor Inc.
Created March 31, 2003 (23 years, 4 months ago)
Expires May 9, 2029 (3 years, 1 months)
Last Updated October 3, 2023
Name Servers ns-1078.awsdns-06.org, ns-1722.awsdns-23.co.uk, ns-344.awsdns-43.com, ns-958.awsdns-55.net
DNSSEC Not enabled
Hosting
IP Address 52.22.128.3
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
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

A+
HTTP Probe Timing
Total 261 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
60 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
66 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
68 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
261 ms
Total Time Total request time from DNS lookup through full response.
261 ms

Connection waterfall

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

Send Feedback