netlify.com
netlify.com describes itself as "Create with AI or code, deploy instantly on production infrastructure. One platform to build and ship.". It was registered in 2014, served from Montreal, Canada. It has a valid HTTPS certificate, 2 of 6 common security headers, 2 tracking scripts.
What is netlify.com about?
The words appearing most often on the homepage, excluding common filler, are a rough indication of subject matter rather than a description of the business:
- netlify ×19
- const ×14
- build ×12
- deploy ×9
- internal ×9
- apps ×8
- await ×8
- json ×8
- platform ×7
- agent ×7
Does netlify.com publish the usual trust pages?
Found: about, contact, privacy. Not found at the usual addresses: terms. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does netlify.com compare with other domains analysed here?
Measured against the 121 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 69% of them (median 790ms) |
|---|---|
| Security headers | More than 88% of them |
| Domain age | Older than 87% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
- npmjs.com
- digitalocean.com
- w3.org
- postman.com
- quikconsole.com
- banneradsites.com
- bettingages.com
- cookiesforlove.com
When was netlify.com registered?
netlify.com was registered on 9 June 2014, which makes it about 12 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Name.com, Inc..
Registration runs until 9 June 2032.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 9 June 2014 |
|---|---|
| Expires | 9 June 2032 |
| Registrar | Name.com, Inc. |
| Registry status | client transfer prohibited |
Where is netlify.com hosted?
The first address resolves to infrastructure in Montreal, Canada.
The network is operated by AWS Global Accelerator (GLOBAL) (AS16509 Amazon.com, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is netlify.com running on?
netlify.com exposes 1 identifiable technology: Google Tag Manager.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Google Tag Manager
The page declares a generator of Astro v5.18.2.
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 552ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 405KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | Netlify |
|---|---|
| Compression | gzip |
| Page size | 415,175 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 36 characters, inside the range that displays without truncation.
A meta description of 102 characters is present.
All 23 images on the homepage have alt attributes.
| Title | Push your ideas to the web | Netlify (36 chars) |
|---|---|
| Meta description | Create with AI or code, deploy instantly on production infrastructure. One platform to build and ship. (102 chars) |
| H1 | Push your ideas to the web (1 on the page) |
| Canonical | https://www.netlify.com/ |
| Open Graph title | Push your ideas to the web | Netlify |
| Headings / images | 13 H2s, 23 images (0 without alt text) |
Is netlify.com served over a valid certificate?
The HTTPS certificate is issued by DigiCert Inc and is valid until 2027-02-05, which is 124 days from the date of this check. It covers 6 hostnames.
- netlify.com
- bitballoon.com
- netlifyglobalcdn.com
- *.netlify.com
- *.bitballoon.com
- *.netlifyglobalcdn.com
The certificate has 124 days left to run.
Which security headers does it set?
2 of 6 are set (HSTS, Permissions-Policy). Absent: Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains; preload |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | yes | browsing-topics=() |
How is DNS configured for netlify.com?
| IP addresses | 3.33.186.135, 15.197.167.90, 2a05:d014:58f:6200::1f5, 2a05:d014:58f:6200::1f6 |
|---|---|
| Reverse DNS | afa7f374f51cc8991.awsglobalaccelerator.com, afa7f374f51cc8991.awsglobalaccelerator.com |
| Name servers | ns01.netlifydns.com, ns02.netlifydns.com, ns03.netlifydns.com, ns04.netlifydns.com, dns1.p04.nsone.net, dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net |
| Mail (MX) | aspmx3.googlemail.com (pri 10), alt1.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1), alt2.aspmx.l.google.com (pri 5), aspmx2.googlemail.com (pri 10) |
| SPF | v=spf1 include:_spf.google.com include:amazonses.com include:7477936.spf06.hubspotemail.net -all |
| TXT records | 29 |
netlify.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 5 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to afa7f374f51cc8991.awsglobalaccelerator.com, afa7f374f51cc8991.awsglobalaccelerator.com, which usually names the hosting provider.
Who runs DNS and mail for netlify.com?
DNS is operated by NS1 rather than self-hosted name servers.
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about netlify.com?
3 of 3 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
1 email address appears in the homepage markup, where address-harvesting crawlers will find it.
What has changed on netlify.com?
This domain has been checked 2 times. Only checks where something actually moved are recorded, so each row below is a real change rather than a repeat measurement.
| Checked | HTTP | Response | IP | Headers |
|---|---|---|---|---|
| 4 Oct 2026 | 200 | 552ms | 3.33.186.135 | 2/6 |
| 4 Oct 2026 | 200 | 753ms | 15.197.167.90 | 2/6 |
Changes recorded at the most recent check:
- IP address: 15.197.167.90 → 3.33.186.135
- name servers: ns03.netlifydns.com,ns01.netlifydns.com,ns04.netlifydns.com,dns2.p04.nsone.net → ns01.netlifydns.com,ns02.netlifydns.com,ns03.netlifydns.com,ns04.netlifydns.com
- mail servers: aspmx3.googlemail.com (pri 10),aspmx2.googlemail.com (pri 10),alt1.aspmx.l.google.com (pri 5) → aspmx3.googlemail.com (pri 10),alt1.aspmx.l.google.com (pri 5),aspmx.l.google.com (pri 1)
Can netlify.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 3 named authorities (iodef mailto:security@netlify.com, issue digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226, issue amazon.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 764 bytes and names 8 user-agent groups. It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.netlify.com/sitemap-index.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
Named AI crawlers are explicitly allowed (gptbot, claudebot, perplexitybot, google-extended).
What structured data does the homepage publish?
- Organization
- ImageObject
- Person
- PostalAddress
- ContactPoint
- WebSite
- WebPage
- SpeakableSpecification
- BreadcrumbList
- ListItem
- SoftwareApplication
- Offer
The homepage publishes 12 structured data types: Organization, ImageObject, Person, PostalAddress, ContactPoint, WebSite, WebPage, SpeakableSpecification, BreadcrumbList, ListItem, SoftwareApplication, Offer.
What does netlify.com load from third parties?
The homepage pulls resources from 4 third-party hosts (cdn.cookielaw.org, googletagmanager.com, js.hs-scripts.com, js.hsforms.net). Each one sees the visitor IP and user agent on every page load.
3 cookies are set before any interaction (nf_hp_visitor_id, nf_hp_prompt_hero, nf_hp_one_tap).
The page links or refers to X/Twitter, LinkedIn, YouTube, GitHub.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| nf_hp_visitor_id | yes | no | lax |
| nf_hp_prompt_hero | yes | no | lax |
| nf_hp_one_tap | yes | no | lax |
Does netlify.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both netlify.com and www.netlify.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can netlify.com be crawled?
A sitemap index is served at https://www.netlify.com/sitemap-index.xml listing 1 entries.
The most recent lastmod date is 2026-10-02.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does netlify.com run?
2 tracking scripts detected: Google Tag Manager, HubSpot.
A consent platform is in place (OneTrust), so in the EU and UK these should only fire after the visitor agrees.
How does netlify.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
How are images, fonts and scripts handled?
23 images on the homepage, 23 of them lazy-loaded (100%).
Modern image formats are in use (1 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 8 external stylesheets and 12 external scripts, with 3 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Responses carry Netlify edge headers, so content is served from a CDN rather than straight from the origin.
Is netlify.com accessible and current?
The page uses 5 landmark elements and 64 ARIA attributes.
There are 9 form inputs but only 7 label elements, so some fields may be unlabelled for screen readers.
Can search engines index netlify.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 118 internal and 13 external links across 9 outside hosts.
Visible text is only 2.1% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is netlify.com delivered?
The HTML is served with Cache-Control: public,max-age=0,must-revalidate.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does netlify.com set the usual HTTP security headers?
It sets 2 of 6. The ones not present are: Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy.
Does netlify.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is netlify.com built with?
The homepage exposes these fingerprints: Google Tag Manager. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own netlify.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →