Website profiles · Technology insights · Alternatives

validator.w3.org No paid content found

Categories: Development

W3C's easy-to-use markup validation service, based on SGML and XML parsers.

Visit website

Updated: 2026-09-26 23:33 Language: English (default) Access: Normal

Profile views 2 Outbound visits 1
The W3C Markup Validation Service Full homepage screenshot

Related questions

More questions →
What Is HTML and How Does It Structure a Web Page?

HTML (HyperText Markup Language) is the markup language that gives a web page its structure and content. It tells a browser what each piece of a page is — a heading, a paragraph, a link, an image — rather than how it should look. If you want to understand how any website is built, HTML is the starting point: it's the skeleton that CSS styles and JavaScript animates. This explainer covers what HTML is, how tags and attributes work, how a browser turns it into a visible page, and where you can see it in the wild.

What HTML actually does

HTML is not a programming language. It doesn't perform calculations, make decisions, or run loops. It's a markup language: you wrap content in labels that describe its meaning and role.

That distinction matters. When you write <h1>Welcome</h1>, you're not saying "make this big and bold." You're saying "this is the top-level heading of the page." The browser decides the default appearance, and CSS can override it later. This separation — structure in HTML, presentation in CSS, behavior in JavaScript — is the core organizing principle of the modern web.

Elements, tags, and attributes

An element is the complete unit: an opening tag, the content, and a closing tag. A tag is the label itself, written between angle brackets. An attribute is extra information placed inside the opening tag.

Here's a simple example:

<h1 class="page-title">Welcome to My Site</h1>
<p>This is a paragraph of text with a <a href="https://example.com">link</a> inside it.</p>
<img src="photo.jpg" alt="A description of the photo">

Breaking that down:

Part Example What it does
Opening tag <h1> Marks where the element begins
Attribute class="page-title" Adds extra info the browser or CSS can use
Content Welcome to My Site The actual text or media
Closing tag </h1> Marks where the element ends

A few things to notice. The <a> element uses an href attribute to say where the link points. The <img> element has no closing tag — it's a void element, because it holds no text content. And the alt attribute on the image provides a text alternative, which matters for accessibility and for when the image fails to load.

How a browser reads HTML and renders a page

When you visit a URL, the browser receives the HTML as plain text and works through it in a defined sequence:

  1. Parsing — The browser reads the markup top to bottom and builds a tree structure called the DOM (Document Object Model). Each element becomes a node in that tree.
  2. Applying CSS — Stylesheets are matched against the DOM to determine how each element should look.
  3. Layout — The browser calculates where each element sits and how much space it takes.
  4. Painting — Pixels are drawn to the screen.

The key insight is that the HTML you write is not the page you see. It's a set of instructions the browser interprets. Two browsers given identical HTML will produce nearly identical structure, but their default styling and rendering details can differ slightly — which is one reason developers test across browsers.

How HTML, CSS, and JavaScript divide the work

A typical site uses all three languages, each with a distinct job:

  • HTML — structure and content. "This is a heading. This is a list. This is a form field."
  • CSS — presentation. "Headings are dark blue, 32px, with 16px of space below."
  • JavaScript — behavior. "When the user clicks this button, load more content."

You can build a perfectly readable page with HTML alone. Add CSS and it becomes visually designed. Add JavaScript and it becomes interactive. The same HTML can be restyled completely without touching its structure — which is why the separation is worth respecting rather than inlining styles and scripts everywhere.

Where to see HTML in practice

You don't need any tools to inspect a page's HTML:

  • View source — Right-click anywhere on a page and choose "View Page Source" (or press Ctrl+U on Windows/Linux, Cmd+Option+U on Mac). This shows the raw HTML the server sent.
  • Developer tools — Right-click an element and choose "Inspect." This opens the live DOM, which may differ from the raw source because JavaScript can modify it after the page loads.

Comparing the two is instructive. The raw source is what the server delivered; the inspected DOM is what the browser actually built. On a JavaScript-heavy site, they can look quite different.

A note on where this fits

HTML is the entry point to web work, but it's rarely used in isolation. If you're learning to build for the web, expect to pick up CSS and JavaScript alongside it. If you're simply trying to understand how a site you admire is put together, viewing its source and inspecting elements will show you the HTML structure directly — and that's often the fastest way to connect the abstract markup to a real page.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

Registered in 1994, this domain has about 32 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 Gandi SAS, a widely used domain service provider. The domain uses the common .org extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the w3.org email service. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

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 within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, Referrer-Policy, Permissions-Policy. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies cloudflare without an exact version.

Technology Stack Analysis

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

Search and Social Sharing

No viewport meta tag was detected, which may affect mobile layout behavior. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 33 characters, within a common display range. A meta description is present, with 81 characters.

Hosting and Email

DNSCloudflare
HostingCloudflare
Emailw3.org
Location United States flagUnited States 2606:4700::6812:1613

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionW3C's easy-to-use markup validation service, based on SGML and XML parsers.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 10 disallowed
  • Disallow/check
  • Disallow/feed/check
  • Disallow/checklink?
  • Disallow/mobile/check
  • Disallow/mobile/alpha
  • Disallow/css-validator
  • Disallow/unicorn/check
  • Disallow/http-checker
  • Disallow/i18n-checker/check
  • Disallow/nu

No sitemaps found

Registration details RDAP / WHOIS

RegistrarGandi SAS
Registered1994-07-06
Expires2029-07-05
Domain statusclient delete prohibited、client transfer prohibited
Nameserversjamie.ns.cloudflare.com、pranab.ns.cloudflare.com
DNSSECunsigned

DNS records

TypeNameValueTTLPriority
Avalidator.w3.org104.18.22.19142—
Avalidator.w3.org104.18.23.19142—
AAAAvalidator.w3.org2606:4700::6812:1613300—
AAAAvalidator.w3.org2606:4700::6812:1713300—
MXw3.orgpan.w3.org3005
MXw3.orgpuck.w3.org3005
NSw3.orgjamie.ns.cloudflare.com86400—
NSw3.orgpranab.ns.cloudflare.com86400—
TXTw3.org853C844562300—
TXTw3.organthropic-domain-verification-xwqnyg=KpEpoEkHUmXnsWC0mhnfKFBrr300—
TXTw3.orgca3-d6556337888945edac9c159a068c46a2300—
TXTw3.orggoogle-site-verification=5TpwKtmzdpa5fntQgKHY96mTJ3FiSn9fGp07XKxFsMk300—
TXTw3.orggoogle-site-verification=CZkSL9bXgKDxRmeDnAQorwhaQy3Ji1vTn36bBn5rL-E300—
TXTw3.orggoogle-site-verification=cu9dn6ytlndLOV87MLxedTHxoKTRKk0dUf_jXK8OsTc300—
TXTw3.orggoogle-site-verification=dS4IjfXgopxupUFDAqg3wk94IIZ2GuQ-jW4wiLm69Rg300—
TXTw3.orgv=spf1 mx ip4:34.238.48.92 ip4:34.199.101.240 ip6:2600:1f18:7d7a:2700::/56 include:_spf.google.com ~all300—
CAAw3.org0 iodef "mailto:[email protected]"300—
CAAw3.org0 issue "amazon.com"300—
CAAw3.org0 issue "comodoca.com"300—
CAAw3.org0 issue "digicert.com; cansignhttpexchanges=yes"300—
CAAw3.org0 issue "letsencrypt.org"300—
CAAw3.org0 issue "pki.goog; cansignhttpexchanges=yes"300—
CAAw3.org0 issue "sectigo.com"300—
CAAw3.org0 issue "ssl.com"300—
CAAw3.org0 issuewild "comodoca.com"300—
CAAw3.org0 issuewild "digicert.com; cansignhttpexchanges=yes"300—
CAAw3.org0 issuewild "letsencrypt.org"300—
CAAw3.org0 issuewild "pki.goog; cansignhttpexchanges=yes"300—
CAAw3.org0 issuewild "sectigo.com"300—
CAAw3.org0 issuewild "ssl.com"300—
DMARC_dmarc.w3.orgv=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=1;300—

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectw3.org
IssuerGoogle Trust Services
Valid until2026-12-05T04:37 · Remaining when checked: 69 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=utf-8
servercloudflare
strict-transport-securitymax-age=15552015; preload
x-frame-optionsdeny
x-content-type-optionsnosniff

Identified technologies

Cloudflare