Skip to content
ViewSource

viewsourceonline.com

Read the source of any website, without leaving the page

Paste a URL and get the complete HTML, page speed breakdown, server and TLS details, page info, security grading, and detected technologies — rendered inline in a single view.

Detects stacks such as

  • Next.js
  • WordPress
  • Cloudflare
  • Astro
  • Tailwind CSS
  • Shopify
  • Nginx
  • Google Analytics
  • Vercel
  • React
analysis dimensions
9
accounts required
0
source read limit
5 MB
free, no caps
100%

View source tool

See exactly what any website is serving

Paste a domain to read its full HTML source in-page — plus page speed, server details, page info, security headers, and detected technologies. Nothing is stored.

Try:

Public pages only. We fetch the URL once and discard it — no history, no accounts.

Everything in one view

More than a source dump

Viewing HTML is the starting point. View Source adds the context developers and SEOs actually need — without making you open five different tools.

Full source, in-page

The complete rendered HTML appears right here — no new tab, no redirect, no browser extension.

Syntax highlighting

Tags, attributes, and values are colour-coded against the design system, with fat-free rendering for huge pages.

Find and copy fast

Search the source with highlighted matches, toggle wrapping, copy the whole document, or download it.

Real page speed

DNS, TCP, TLS, server wait, and download are timed on the server — the numbers a browser waterfall would show.

Server intelligence

IP address, web server, CDN, cache status, compression, HTTP version, and the full TLS certificate.

Page info at a glance

Title, description, canonical, language, charset, viewport, favicon, heading outline, and element counts.

Smart analysis

SEO checks, Open Graph, Twitter Cards, structured data, hreflang, links, and resource breakdowns.

Security headers

HSTS, CSP, X-Frame-Options, and cookie flags graded A–F, with a concrete fix for every gap.

Technology detection

Frameworks, CMS platforms, analytics, CDNs, and runtimes — each with the evidence that triggered it.

How it works

Three steps, one page

  1. 01

    Paste a URL

    Type a domain or a full URL. We add https:// for you and validate the host before fetching.

  2. 02

    We fetch and measure

    Your server requests the page once, timing DNS, TCP, TLS, TTFB, and download along the way.

  3. 03

    Read everything in place

    Source, speed, server, page info, SEO, security, and technologies render on this same page.

Page speed

Every phase, separately measured

A single "load time" number hides where the delay lives. We break the request into its constituent phases so you can see whether the problem is DNS, the network, the TLS handshake, or a slow backend.

If a CDN cf-cache-status orx-cache header is present, we surface the edge cache verdict alongside it.

PhaseWhat it tells you
dnsResolving the domain to an IP address.
tcpOpening the transport connection to the origin.
tlsNegotiating encryption and validating the certificate.
ttfbTime to first byte — how long the backend took to respond.
downloadTransferring the HTML payload to our server.

Why View Source

The same idea, executed further

Viewing page source is a solved problem. Understanding what you are looking at is not. Every feature below exists because the current options stop one step short.

One page, zero redirects

Competitors push you to /html-viewer, /seo-checker, and /download pages. Here the source, metrics, and audit all render on the page you started on.

Ours
Results inline
Others
Separate tool pages

Evidence-backed tech detection

Every detected technology lists what triggered it — an HTTP header, cookie, markup pattern, or asset URL. No black-box "100+ technologies" claim.

Ours
Shows the evidence
Others
Bare name list

Real transport timing

DNS, TCP, TLS, TTFB, and download are probed with real sockets, not inferred from one fetch call. You see TLS version, cipher, issuer, and certificate expiry.

Ours
Socket-level detail
Others
Single aggregate

Security graded, not listed

Missing HSTS, CSP, or cookie flags come with the exact header to add and a severity-weighted grade from A+ to F.

Ours
Actionable fixes
Others
Raw header dump

Private by construction

The URL and source are never written to a database or log. Requests are stateless and discarded when the response is returned.

Ours
No storage at all
Others
"May be cached"

Built to be read

Tight display type, mono eyebrows, hairline structure, and a genuine dark theme make long documents comfortable — rather than a wall of colour.

Ours
Designed type system
Others
Default table styling

Guides

View source, audit, and inspect — in one place

View Source Online combines the tools developers and SEOs usually have to piece together. Here is what each one does and when to reach for it.

How to view page source online

Paste any URL into the field above and press View source. The page is fetched once by our server and its complete HTML is rendered inline — no new tab, no view-source: shortcut, and no browser extension. This works in Chrome, Firefox, Safari, and Edge, and on phones and tablets where the native command is unavailable.

View source code on mobile

Most mobile browsers have never supported the view-source: prefix, so reading a page’s HTML on a phone usually means switching to a desktop. View Source Online works in any mobile browser: enter a domain, and the full source renders with syntax highlighting, search, copy, and download — all responsive to a small screen.

Free on-page SEO audit

Alongside the raw HTML you get a scored SEO audit: title and meta description length, canonical tag, heading outline, Open Graph and Twitter Card tags, structured data, hreflang, internal and external links, and image alt coverage — each check graded pass, warning, or fail with a concrete fix.

Check HTTP security headers

Every response is graded A+ to F on its security posture. HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and cookie flags are inspected, and each missing header comes with the exact value to add.

Detect the technologies a site uses

We identify frameworks, CMS platforms, JavaScript libraries, analytics, CDNs, and runtimes from headers, cookies, markup patterns, and asset URLs — and show the evidence that triggered every match, so you can verify the result rather than trust a black box.

See where load time goes

A single “load time” number hides the cause of a slow page. We time DNS lookup, TCP connect, TLS handshake, server wait (TTFB), and download with real sockets, and surface the CDN edge cache verdict when a cf-cache-status or x-cache header is present.

FAQ

Questions, answered

Still unsure about something? These are the things people ask most before analyzing their first page.

Is View Source Online really free?

Yes. Every feature — source viewing, page speed, server info, page info, the SEO audit, security grading, and technology detection — is free and requires no account.

Do you store the URLs or source code I analyze?

No. The request is stateless: we fetch the page, analyze it in memory, return the result, and discard it. Nothing is written to a database, and submitting a URL never creates a history entry.

How is this different from the browserʼs view-source: command?

view-source: shows raw HTML as your browser received it. We do the same but add syntax highlighting, in-page search, copy and download, plus page speed timings, server and TLS details, an SEO audit, security header grading, and technology detection — and it works on mobile, where view-source: is unavailable.

Which pages can be analyzed?

Any public http or https URL that returns HTML. Pages behind a login, private and local network addresses, and non-HTML content types (images, PDFs, JSON APIs) are rejected by design.

Can I view the source of a page that blocks bots?

Sometimes. We send a normal browser user agent and follow up to eight redirects, but sites that aggressively block automated traffic may still refuse the request. When that happens we tell you which failure occurred — DNS, connection, TLS, timeout, or HTTP error.

Why does the page speed differ from my own measurement?

Timings are measured from our server to the origin, so they exclude your local network, device, and browser rendering. They are best read as a comparison baseline — the relative split between DNS, TLS, server wait, and download is the useful signal.

Does it work on mobile?

Yes. Mobile browsers have never supported view-source:, so this is often the only way to read a pageʼs HTML on a phone or tablet. The interface is fully responsive, with the source viewer scrollable and wrap enabled on demand.

Is the source code modified in any way?

No. What you see is exactly what the server returned — nothing is executed, normalized, or rewritten. Large documents over 5 MB are truncated for display, and the viewer tells you when that happens.