Website profiles · Technology insights · Alternatives

couleur.io

A simple color tool to help you find good color palettes for your web projects. This tools spits out modern CSS you can use right away in your projects.

No paid content found
Visit website
Profile views 11 Outbound visits 2 Normal
couleur.io → Harmonizing Color Palettes for Your Web Projects Full homepage screenshot

At a glance

Category
Color Tools
Language
English
Paid-content signal
No paid content foundObserved
Registered
2016
Hosting
NetlifyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is couleur.io?

couleur.io is a browser-based color tool for building harmonized palettes and copying the result straight into a web project as CSS. You choose a starter hue and a saturation level, and it generates a 10-swatch palette by varying lightness across that hue and saturation, so the colors share a consistent character rather than looking randomly assembled.

It also suggests accent colors by rotating the base hue in 45-degree steps. The site notes that 45° or 315° rotations may not contrast enough, while 90°, 135° or 180° usually work better. A preview panel shows the palette in a light and dark page context—headings, body text, links, a sample article layout—so you can judge it against realistic UI rather than isolated chips.

The CSS-variable angle

The output is framed around HSL values and CSS variables. You can copy a set of variables, then adjust --base-hue, --base-sat and --primary-lightness to shift the whole palette at once, or --accent-hue and --accent-lightness to change just the accent. That makes it useful for a small site or prototype where you want a coherent theme without hand-picking every shade.

Who it suits

  • Developers who want a quick palette plus ready-to-paste CSS variables.
  • Designers who already have a brand hue and need a lightness ramp plus accent options.
  • Anyone building a simple site who wants to test colors in a realistic light/dark preview.

The trade-off: it is deliberately narrow. It works from one hue and one saturation, so it won't produce multi-hue, earthy or highly desaturated schemes, and it isn't a full design system or contrast checker. If you need WCAG contrast verification, check the final text/background pairs separately.

A practical next step: pick your brand hue, set saturation to a moderate level, preview in dark theme, then copy the variables and test them in your actual layout. For broader palette inspiration alongside it, Coolors and Color Hunt are established options.

How does couleur.io generate harmonizing color palettes?

couleur.io builds a palette from two inputs you choose: a starter hue (0–360 on the color wheel, where 0 and 360 are both red) and a saturation level (0–100%). From that single hue-and-saturation pair it produces 10 swatches by varying only lightness. Because every swatch shares the same hue and saturation, the set stays visually related rather than clashing.

How the accent colors are derived

The tool rotates the base hue in 45-degree increments to suggest accent colors. Its own guidance notes that a 45° or 315° shift may be too close to the base to read as a real contrast, while shifts of 90°, 135° or 180° usually work better for accents.

What you get out

  • Individual swatches you can pick from.
  • A set of CSS variables for the full palette, which you can paste into your project.
  • Global controls: adjusting --base-hue, --base-sat and --primary-lightness shifts the whole palette at once, while --accent-hue and --accent-lightness change just the accent.
  • A preview in context, including a dark-theme preview, so you can judge the colors on a realistic page layout before committing.

A practical way to use it

Start with your brand's dominant hue, set saturation to a moderate level, then scan the 10 lightness steps for a background, a surface, body text and a border. Pick an accent at a 90–180° rotation rather than the nearest 45° step, and test it against both the light and dark previews. If the accent feels weak, nudge --accent-lightness rather than changing the hue.

For comparison, Coolors is built around generating and locking individual colors, whereas couleur.io is narrower: one hue, one saturation, lightness-driven steps, and CSS variables as the deliverable. If you want a controlled, systematic scale, couleur.io's approach is the closer fit.

How can I use the CSS variables from couleur.io in my web project?

Use the generated CSS custom properties as a small design-token layer: set them once near the top of your stylesheet, then reference them by role (background, text, border, accent) throughout your components. The palette is built in HSL, so each color shares the same hue and saturation and only the lightness step changes. That is what makes the set feel like one family rather than ten unrelated swatches.

A practical starting point

:root {
  --base-hue: 210;
  --base-sat: 60%;
  --primary-lightness: 45%;
  --accent-hue: 300;
  --accent-lightness: 55%;
}

Then map the palette swatches to semantic names instead of using the raw steps everywhere:

:root {
  --surface: hsl(var(--base-hue) var(--base-sat) 96%);
  --text: hsl(var(--base-hue) var(--base-sat) 15%);
  --brand: hsl(var(--base-hue) var(--base-sat) var(--primary-lightness));
  --accent: hsl(var(--accent-hue) var(--base-sat) var(--accent-lightness));
}

The advantage of this two-layer approach is that changing --base-hue re-tints the whole interface at once, while your components keep reading stable names like --surface. If a rebrand or seasonal theme arrives, you edit two or three numbers rather than hunting through every rule.

Choosing an accent that actually contrasts

The tool generates accent ideas by rotating the base hue in 45-degree steps. Its own guidance is worth following: a 45 or 315 degree shift is often too close to the base to read as an accent, while 90, 135 and 180 degrees usually separate clearly. If your accent is used for buttons, links or focus rings, check it against the background at the lightness values you actually ship, not just in the swatch grid. A hue rotation changes the color but not the lightness contrast, so you may still need to nudge --accent-lightness for accessible text.

Where this fits and where it does not

This approach suits marketing sites, blogs, dashboards and prototypes where you want a coherent, quickly adjustable palette. It is less suited to projects that need a full multi-hue brand system, precise brand-mandated hex values, or a large semantic token set with success, warning and error states — you would layer those on top yourself.

For related reference, MDN Web Docs documents HSL and custom property behavior, and WebAIM covers the contrast checking you should run before shipping.

Which accent color hue rotations work best for contrast?

Rotations of 90°, 135° and 180° from the base hue usually give the most reliable contrast. Rotations of just 45° or 315° are the weakest options — they sit too close to the base hue to separate clearly.

That guidance comes from the tool's own notes on couleur.io, which generates accent ideas by rotating the starter hue in 45° steps. The reasoning is straightforward: the further you move around the hue circle, the more the accent diverges from the base, until you approach the opposite side.

H3 Practical way to choose

  • 45° / 315° — subtle, tonal shifts. Fine for hover states, borders or backgrounds where you want variation without a jolt. Poor for buttons or links that must stand out.
  • 90° / 135° — strong, clearly distinct accents that still feel related to the base. Good default for interactive elements.
  • 180° — maximum hue separation; the classic complementary pairing. Highest contrast, but also the most likely to look loud if both colors are highly saturated.

H3 A concrete scenario

Say you're building a marketing site with a blue base hue. A 45° rotation lands on a neighbouring blue-violet — your call-to-action button will blend into the page. Rotating 135° gives you a warmer, contrasting accent that reads as a deliberate highlight. If you go 180°, you get an orange accent that pops hard; it works for a single primary button, but using it for every link and badge will feel aggressive.

H3 Decision criterion

Match the rotation to how much attention the element needs. Small, frequent UI (links, tags, focus rings) suits 90–135°. One hero element per screen can carry 180°. Reserve 45° and 315° for states and surfaces rather than for anything the user must find.

If you want to see the trade-off rather than reason about it, the site's preview panel renders a palette in a light and dark page context, which is the quickest way to judge whether an accent actually holds up against real text and backgrounds.

How do I preview a color palette in dark theme context?

Use the preview in dark theme context option in couleur.io's palette preview area. The page shows a light preview and a dark-theme preview side by side, each rendering the same sample layout (nav links, a headline, body text, a "read more" link) so you can see how your chosen colors behave on a dark background.

Couleur.io

What the dark preview actually shows you

  • The same 10-swatch palette applied to text, links and UI elements over a dark surface.
  • Whether your base hue and saturation still read as intended when lightness is inverted.
  • How the generated accent colors hold up against dark backgrounds.

Practical checks to run in it

  1. Set --base-hue and --base-sat first, then look at both previews before touching anything else.
  2. Inspect the accent color specifically. The tool notes that accents rotated only 45 or 315 degrees from the base hue may not contrast enough; 90, 135 or 180 degrees usually work better. Dark themes punish weak contrast faster than light ones.
  3. Toggle the CSS variables for the full palette and copy them once both previews look right.
  4. Re-check --primary-lightness and --accent-lightness after copying — adjusting these two values shifts the whole palette at once, which is the fastest way to fix a dark-mode-only problem.

A concrete scenario

You're building a blog with a light default and a dark mode toggle. Pick a starter hue, refine saturation, then compare the two previews. If the body text looks fine in light but muddy in dark, raise --primary-lightness rather than re-picking the hue — the hue and saturation stay harmonized, and both themes keep the same color identity.

Decision criterion

If your project ships both themes, treat the dark preview as the stricter test: colors that pass there almost always pass in light. If you only ship a dark theme, skip the light preview entirely and tune directly against the dark one.

What is the subscription option for couleur.io?

couleur.io is a free browser-based color tool for building harmonized HSL palettes, and its only visible subscription-like element is a “subscribe” prompt embedded in the blog/article preview. The page evidence does not describe a paid plan, account tier, newsletter, or billing platform behind it, so there is no confirmed subscription product to describe.

The practical takeaway: treat “subscribe” as a generic call-to-action rather than a signup requirement. If you want to evaluate the tool, open couleur.io and test the core workflow without creating an account: pick a starter hue, adjust saturation, preview the palette in light and dark article contexts, and copy the CSS variables.

A useful decision criterion: if you need a palette generator with immediate CSS output and no signup friction, this fits. If you need saved team libraries, version history, or account-based collaboration, the visible page evidence does not show those features.

Related questions

More questions →
Can I preview a couleur.io palette in real page and dark theme contexts?

Yes. couleur.io includes a built-in preview that applies your generated palette to sample page content, and it also offers a dark theme version of that same preview. You can judge contrast and readability in both before copying any CSS.

What the preview shows

The preview renders a small mock webpage rather than isolated color swatches. Based on the tool's page, the sample content includes:

  • A navigation row with home, about, and contact
  • An article-style block with a heading ("A tale of two animals"), a date line, and body paragraphs
  • A read more link and a subscribe element

This matters because swatches alone don't tell you whether your accent color survives contact with real text. Seeing the palette on headings, body copy, links, and buttons shows you where contrast actually holds up.

Light and dark theme contexts

The tool provides two preview modes:

Preview mode What it's for
Standard (light) context Checking the palette against a light background
Dark theme context Checking the same palette against a dark background

Because the palette is built from a single hue and saturation with varying lightness, the dark theme preview is where you'll usually spot problems first — a lightness step that reads fine on white can disappear or glare on a dark surface.

How to use it to make a decision

  1. Pick a starter hue — a value from 0 to 360.
  2. Refine saturation — a value from 0% to 100%.
  3. Look at the palette — 10 swatches generated from varying lightness levels on that hue and saturation.
  4. Check the preview in context — read the sample page in the standard view, then switch to the dark theme view.
  5. Judge the accent color specifically — see the note below.
  6. Copy the CSS variables if it holds up, or adjust and re-check.

What to look for when judging

The preview is most useful for these checks:

  • Body text against background — is the paragraph copy still comfortable to read?
  • Headings vs. body — do they separate clearly, or blur together?
  • Links and "read more" — does the accent color stand out from surrounding text without vibrating against it?
  • The subscribe/button element — is it obviously interactive?
  • Dark theme — does anything become unreadable or overly harsh?

A caveat about accent colors

The tool generates accent ideas by rotating the base hue in 45-degree increments. Its own guidance notes that accents only 45 or 315 degrees from the base hue may not contrast enough with the base color. Accents at 90, 135, or 180 degrees of difference usually work better.

So when you preview, don't assume every accent option is equally viable — test the wider rotations first, and use the preview to confirm the one you pick actually separates from the base in both themes.

Tuning without starting over

If the preview reveals a problem, you don't have to rebuild the palette. The generated CSS variables let you adjust globally:

  • --base-hue, --base-sat, and --primary-lightness shift the whole palette at once
  • --accent-hue and --accent-lightness shift just the accent color

Change one value, then re-check the preview in both themes. This is the fastest loop: adjust a variable, look at the sample page, repeat until the contrast reads well in light and dark.

Bottom line

Use the preview as your go/no-go check. If the palette reads clearly on the sample page in both the standard and dark theme contexts — especially the accent against body text and UI elements — it's a reasonable foundation to copy into your project. If the accent only works in one theme, adjust --accent-hue or --accent-lightness before committing.

How to Use couleur.io to Generate CSS Variables for Your Website

couleur.io generates a 10-swatch color palette from a single starter hue and saturation level, then outputs CSS variables you can paste directly into your stylesheet. It's a good fit if you want a harmonized palette without picking ten colors by hand, and if you're comfortable editing HSL values in CSS. The tool works in the browser and requires no build step — you pick a hue, refine saturation, preview the palette in a light and dark page context, then copy the variables.

What the tool actually produces

The palette is built entirely from HSL. You choose:

  • A starter hue — a value from 0 (red) to 360 (red again)
  • A saturation level — a value from 0% to 100%

From those two inputs, couleur.io creates 10 swatches by varying lightness while keeping hue and saturation fixed. Because every swatch shares the same hue and saturation, the colors are harmonized by construction rather than by eye.

Accent colors are generated separately by rotating the base hue in 45-degree increments. One caveat from the tool's own documentation: accents only 45 or 315 degrees from the base hue may not contrast enough. Rotations of 90, 135, or 180 degrees usually work better as accents.

Step-by-step: from hue to CSS variables

1. Pick a starter hue

Set the base hue to match the dominant color you want for your site. If you're matching an existing brand color, convert it to HSL first and use its hue value here.

2. Refine saturation

Adjust saturation to control how vivid or muted the whole palette feels. This single value affects all 10 swatches, so it's the fastest lever for going from "loud" to "understated."

3. Preview the palette in context

The tool renders the palette against a sample page — a nav, headings, body copy, and a "read more" link — in both a light and a dark theme context. Use this to check whether your text and accent colors hold up before you commit. This is the step most people skip, and it's the one that catches unreadable combinations early.

4. Copy the CSS variable set

Toggle the CSS variables option to get the full palette as variables, then paste them into your stylesheet. The tool notes this variable-composition approach is inspired by Maxime Heckel's writing on CSS variable composition.

5. Apply the variables in your CSS

Once the variables are in your stylesheet, reference them anywhere you'd normally hardcode a color:

:root {
  /* pasted from couleur.io */
  --base-hue: 210;
  --base-sat: 60%;
  --primary-lightness: 45%;
  --accent-hue: 345;
  --accent-lightness: 50%;
}

.button {
  background: hsl(var(--base-hue) var(--base-sat) var(--primary-lightness));
}

.button--accent {
  background: hsl(var(--accent-hue) var(--base-sat) var(--accent-lightness));
}

The exact variable names and count come from the tool's output — paste it as-is rather than retyping, since the palette swatches are derived from these values.

Tuning the palette after you paste it

The point of the variable set is that you can shift the entire palette by editing a few values instead of ten colors:

Change this Effect
--base-hue Rotates every base swatch to a new hue at once
--base-sat Makes the whole palette more vivid or more muted
--primary-lightness Moves the primary color lighter or darker
--accent-hue Changes only the accent color's hue
--accent-lightness Changes only the accent color's lightness

Because hue and saturation are shared across the base swatches, changing --base-hue or --base-sat keeps the palette harmonized — you can't accidentally break the relationship between colors. Changing --accent-hue is the one edit that can reduce contrast against the base, so re-check it against your background after adjusting.

Common snags

  • Accent looks too similar to the base. You likely picked a 45- or 315-degree rotation. Move toward 90, 135, or 180 degrees.
  • Text is hard to read in the preview. Adjust --primary-lightness before copying, or plan to use a different swatch from the 10 for text versus backgrounds.
  • Colors look right in light mode but wrong in dark. Check the dark theme preview before finalizing — the same lightness values behave differently against a dark background.
  • You want one specific color to stay fixed. The palette is generated, not hand-picked, so if a brand color must be exact, set it as a separate variable and use the generated palette for everything else.

When this approach fits

Use couleur.io if you want a coherent palette fast and you're working in CSS with HSL values. Skip it if you need precise control over each individual color, if your project uses a design system with locked tokens, or if you need CMYK or print-accurate values — the tool is built around HSL for web use.

How couleur.io Creates Harmonized Color Palettes and Accent Colors

couleur.io builds a palette from two inputs: a starter hue (0–360) and a saturation level (0–100%). It then generates 10 swatches by varying lightness while keeping hue and saturation fixed, which is why the colors read as harmonized rather than random. Accent colors come from rotating that base hue in 45-degree increments, and the tool itself notes that 90, 135, or 180-degree shifts usually contrast better than 45 or 315.

The core mechanism: one hue, one saturation, ten lightness steps

The tool works in HSL, so each color is defined by three separate values instead of a single hex code. That separation is what makes the palette predictable:

  • Hue stays constant across the whole palette, so every swatch is recognizably the same color family.
  • Saturation stays constant too, so no swatch suddenly looks washed out or neon relative to its neighbors.
  • Lightness is the only variable, stepped across 10 levels to produce the swatch range.

Because only one dimension changes, the result is a set of colors that share a visual identity. This is the practical difference between a harmonized palette and a hand-picked one: you get consistency by construction, not by trial and error.

Why HSL matters here

In HSL, hue is a degree on a color wheel (0 and 360 are both red), saturation is a percentage, and lightness is a percentage. Adjusting lightness alone moves a color from near-black through the pure hue to near-white without shifting its character. That is exactly the behavior you want when you need a range of tints and shades for backgrounds, borders, text, and buttons that all belong together.

How accent colors are generated

Accent colors are produced by rotating the selected base hue by increments of 45 degrees. So from a base hue you get candidate accents at +45, +90, +135, +180, and so on around the wheel.

The tool is explicit about which of these tend to work:

Hue shift from base Contrast quality
45° or 315° May not contrast enough with the base hue
90°, 135°, or 180° Usually work well as accents

The reason is straightforward: small rotations land close to the base color, so the accent reads as a slightly-off version of the same color rather than a distinct one. Larger rotations move far enough around the wheel to separate clearly while still relating to the original hue.

Using the output in a real project

The tool outputs modern CSS you can use directly. Two ways to work with it:

  1. Pick individual colors from the 10-swatch palette when you only need a few specific values.
  2. Copy the full set of CSS variables as a foundation for your project's color system.

If you take the CSS variables route, the tool exposes a few control points that let you retune the whole palette at once:

  • --base-hue — shifts every color in the palette to a new hue family.
  • --base-sat — raises or lowers saturation everywhere simultaneously.
  • --primary-lightness — moves the primary color up or down the lightness range.
  • --accent-hue and --accent-lightness — adjust the accent color independently of the base palette.

This is the practical payoff of the HSL approach: changing one variable re-harmonizes the entire set instead of forcing you to re-pick each color.

Checking a palette before you commit

The tool includes a preview that renders the palette in context — a sample page with navigation, headings, body text, and a "read more" link — and it also offers a dark theme preview. Use it to answer questions that swatches alone can't:

  • Does the accent still stand out against the base when used for links or buttons?
  • Does body text remain readable on the lightest and darkest swatches?
  • Does the palette hold up when the surrounding UI flips to dark?

The dark theme preview is worth running even if you're only building a light interface, because it shows whether your lightness steps leave room for an inverted version later.

Where this approach fits and where it doesn't

couleur.io is a good fit when you want a coherent single-hue system quickly, or when you need a defensible accent color without guessing at complementary pairs. It is a lighter-weight option than a full design-token pipeline, and the CSS variable output drops into most projects without conversion.

It is less suited to palettes that intentionally span multiple unrelated hues, or to work that requires precise brand color matching — since the palette is derived from a hue and saturation you choose, not from fixed brand values. In those cases you'd use the tool as a starting point and then pin specific swatches to your required colors.

One caveat the tool states directly: don't assume a 45-degree accent will read as an accent. If the contrast looks weak in the preview, step out to 90, 135, or 180 degrees before adjusting anything else.

What couleur.io Is and How It Helps You Build Web Color Palettes

couleur.io is a browser-based color tool that generates a harmonized 10-swatch palette from a single starter hue and saturation level, then outputs CSS variables you can paste directly into a web project. It suits anyone who needs a coherent color scheme quickly — a landing page, a small site, a prototype — without hand-tuning ten separate colors. If you need brand-accurate colors or a full design system, it's a starting point rather than a final answer.

How the palette is generated

The tool works in HSL, which is what makes the output predictable:

  • You pick a starter hue — a value from 0 (red) to 360 (red again).
  • You pick a saturation level — a value from 0% to 100%.
  • The tool then produces 10 color swatches by varying lightness across that fixed hue and saturation.

Because every swatch shares the same hue and saturation, the colors are harmonized by construction. You aren't judging whether ten arbitrary colors "go together" — you're choosing how light or dark each step should be.

Accent colors and how they're derived

Accent suggestions come from rotating the base hue in 45-degree increments. That produces colors that can contrast with the base in a pleasing way, but the tool itself flags a caveat worth repeating:

Hue rotation from base Practical note
45° or 315° May not contrast enough with the base hue
90°, 135°, 180° Usually work well as accents

So if you want a clear accent, start from the 90/135/180 options rather than the nearest rotation.

Previewing in context

The tool renders the palette against sample page content — headings, body text, links, a "read more" — in both a light and a dark theme context. This matters because a palette that looks balanced as swatches can fail once text sits on top of it. Checking both contexts before committing is the main reason to use the preview rather than just eyeballing the swatches.

Using the CSS output

The tool can output a set of CSS variables for the full palette, which you paste into your stylesheet as a foundation. The variables are composed so that a few values drive everything:

  • --base-hue, --base-sat, --primary-lightness — adjusting these shifts the entire palette at once.
  • --accent-hue, --accent-lightness — adjusting these shifts only the accent color.

That composition means you can retheme a project by changing two or three numbers instead of editing ten color values. You can also toggle CSS variables for the full palette on and off in the interface, and pick individual colors from the palette if you only need a few.

When to use it, and when not to

Good fit:

  • You have a rough idea of a hue and want a usable, consistent set of shades fast.
  • You want CSS variables rather than a static image of a palette.
  • You're prototyping and want light/dark context checks built in.

Poor fit:

  • You need exact brand hex values — HSL-derived swatches won't match a fixed brand spec.
  • You need semantic naming (success, warning, surface) — the output is a palette, not a token system.
  • You need accessibility contrast guarantees — the preview shows context, but it isn't a contrast checker, so verify text/background pairs separately.

A quick workflow

  1. Pick a starter hue and saturation that roughly match the mood you want.
  2. Scan the 10 swatches and the light/dark previews to see how text and links read.
  3. Choose an accent from the 90°, 135°, or 180° rotations if you need visible contrast.
  4. Copy the CSS variables into your stylesheet.
  5. Tweak --base-hue, --base-sat, and --primary-lightness to shift the whole palette, and --accent-hue / --accent-lightness for the accent alone.

The site notes a "subscribe" element in its page content, so some parts of the experience may involve signing up — the palette generation and CSS output described above are what the tool documents as its core function.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2016, this domain has about 10 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is GoDaddy.com, LLC, a widely used domain service provider. The domain uses the common .io extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by NS1, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed. The lowest observed DNS TTL is 120 seconds.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Netlify. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies Alpine.js, Netlify without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Twitter Card metadata is configured. The title has 61 characters, within a common display range. A meta description is present, with 152 characters. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.

Hosting and Email

DNSNS1
HostingNetlify
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagAshburn, Virginia, United States Inferred 18.208.88.157

Registration details

RDAP / WHOIS

RegistrarGoDaddy.com, LLC
Registered2016-07-27
Expires2027-07-27
Domain statusclientDeleteProhibited https://icann.org/epp#clientDeleteProhibited、clientRenewProhibited https://icann.org/epp#clientRenewProhibited、clientTransferProhibited https://icann.org/epp#clientTransferProhibited、clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Nameserversdns1.p03.nsone.net、dns2.p03.nsone.net、dns3.p03.nsone.net、dns4.p03.nsone.net
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Acouleur.io18.208.88.157120—
Acouleur.io98.84.224.111120—
NScouleur.iodns1.p03.nsone.net3600—
NScouleur.iodns2.p03.nsone.net3600—
NScouleur.iodns3.p03.nsone.net3600—
NScouleur.iodns4.p03.nsone.net3600—
TXTcouleur.ioahrefs-site-verification_a7cfc6326d531294608263afa8d5c514cd9f144072a2b54889e3b1d3d09779213600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectcouleur.io
IssuerLet's Encrypt
Valid until2026-12-29T18:31 · Remaining when checked: 85 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlpublic,max-age=0,must-revalidate
serverNetlify
strict-transport-securitymax-age=31536000

Identified technologies

Alpine.jsNetlify

Pages, Search and Sharing

Meta descriptionA simple color tool to help you find good color palettes for your web projects. This tools spits out modern CSS you can use right away in your projects.
Canonical URLhttps://couleur.io/
LanguageEnglish (default)
Twitter Cardsummary_large_image

No robots.txt found

No sitemaps found

User reviews (0)

  • No reviews yet.