Website profiles · Technology insights · Alternatives

catonmat.net

catonmat.net

No paid content found
Visit website
Profile views 6 Outbound visits 1 Normal
catonmat.net Full homepage screenshot

At a glance

Category
Other
Language
English
Paid-content signal
No paid content foundObserved
Registered
2005
Hosting
Akamai Connected CloudInferred
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 catonmat.net?

catonmat.net is the personal blog of Peteris Krumins, and the page in question is a post announcing a redesigned user interface for Browserling, his browser-testing service. In other words, the site itself is a blog about programming, command-line tools and software projects, while this particular page documents a product update rather than offering a general introduction to the site.

What the page covers

  • An announcement of a new, single-menu interface for Browserling
  • Menu controls for choosing an operating system and browser version
  • A URL field for loading a site directly in the chosen browser
  • Display options for zooming and changing resolution, including responsive testing
  • Screen capture with annotation tools such as pen, rectangle, text and eraser
  • Additional features listed: local testing via an SSH tunnel to localhost or a local network, an on-screen keyboard, sharing a browser link, and sending feedback

Who it is useful for

The post is aimed at people who already use or are curious about Browserling: web developers checking how a site renders across browsers, testers who need a quick screenshot with annotations, and anyone who wants to try a site on a platform they do not have locally. A reader who only wants to understand what catonmat.net is will find the broader blog more relevant than this single announcement.

A practical next step

If cross-browser checking is your goal, open the linked Browserling session described in the post and try the workflow end to end: pick an operating system and browser, load your own site through the URL field, change the resolution to a mobile width, then capture and annotate a screenshot. That sequence exercises most of the features the post describes and shows quickly whether the tool fits your testing routine. For related browser-based testing options, see BrowserStack and LambdaTest.

How do I test my website on different browsers using catonmat.net's Browserling tool?

Open catonmat.net and use the Browserling link there to start a session in a specific browser, then test your site directly inside that remote browser. The tool's own interface is built around one menu: pick the platform and browser at the top, enter your URL, and use the feature buttons at the bottom for display, screenshots, and local testing.

A practical test flow

  1. Choose the target. In the menu, select the operating system and browser version you want to check, such as an older Chrome, Firefox, Safari or Edge. Loading a version takes a click or two.
  2. Enter your URL. Type your site's address into the URL navigation field and click go; the browser opens and loads the page.
  3. Resize and zoom. Use display options to change the resolution and zoom level. This is how you check responsive breakpoints and how the site looks on a 4K screen, a small laptop, or a phone-sized viewport.
  4. Repeat across browsers. Work through the browsers your audience actually uses, noting layout breaks, font differences, and JavaScript errors each time.
  5. Capture what you find. The screen capture feature takes a screenshot of a selected browser region, then lets you annotate it with a pen, rectangle, text, or eraser before sharing it with a developer or client.
  6. Test local or private pages. If your site isn't public yet, the local testing feature opens an SSH tunnel to localhost or your local network so the remote browser can reach it. The on-screen keyboard helps when you're on a non-English keyboard or a mobile device, and "share a browser" sends someone a link to the current browser and page.

Deciding when this fits

Browserling is a hosted browser service, so it suits quick cross-browser checks, client demos, and verifying a page on a browser you can't install locally. It's less suited to automated regression suites or debugging that needs deep access to your own machine's dev tools and network stack — for those, a local setup or a dedicated testing framework is usually a better fit. Also keep in mind that a remote session renders your site on the service's infrastructure, so network conditions and geolocation may not match your users'.

A useful next step: list the browser/OS combinations from your analytics, test the top three first, and capture annotated screenshots of any breakage so the fix is unambiguous.

Can I use catonmat.net to test a local website running on my computer?

Yes, but not by pointing the browser directly at your own localhost. The page evidence describes a local testing feature in the new Browserling interface that "allows opening an ssh tunnel to localhost or local network to test local websites." That is the intended path: the remote browser reaches your machine through a tunnel rather than you running the browser locally.

What that means in practice

If you are building a site on http://localhost:3000 and need to see it in a specific browser or platform, you would:

  1. Start your local server as usual.
  2. Open the Browserling interface and load the browser/platform you need.
  3. Use the local testing feature to open the tunnel to localhost or your local network.
  4. Navigate to the local address and test.

Limits worth knowing

  • The tunnel is the mechanism, not a general "open my localhost" button, so expect a setup step rather than typing localhost straight into the URL field.
  • Local testing is described as one of the features in the menu, alongside display options, screen capture, on-screen keyboard, and sharing a browser link. The page does not detail tunnel setup requirements, supported ports, or whether it works behind restrictive corporate networks, so treat those as things to verify before relying on it for daily work.
  • For quick local iteration, a browser already installed on your machine is simpler. The remote-browser route makes more sense when you specifically need a browser or platform you do not have locally.

A useful next step

If your goal is cross-browser checking of a site you are actively developing, try the tunnel once with a trivial page first. That tells you whether your network and firewall cooperate before you depend on it during a deadline. For related browser-testing options, BrowserStack and LambdaTest also offer hosted real-browser testing with local-connection features, and catonmat.net itself is the blog where this interface change was announced.

How do I take and edit screenshots of a browser session on catonmat.net?

You take screenshots through Browserling's capture-screen feature, not through catonmat.net itself. The blog post on catonmat.net describes the tool: after selecting the browser region you want, it opens the screenshot and gives you editing tools including a pen, rectangle, text annotation and eraser.

A practical workflow

  1. Open the page you want to capture in a Browserling browser session.
  2. Use the menu's capture-screen feature and select the region of the browser to save.
  3. Annotate the captured image with the pen, rectangle, text or eraser tools.
  4. Copy the result to your clipboard or save it, depending on the options shown.

The same post also mentions display options that let you zoom and change the browser resolution. That matters for screenshots: if you're on a 4K monitor, zooming in before capturing avoids tiny, unreadable text, and resizing the viewport lets you capture the same page at different screen sizes for responsive testing.

Who this suits

This is most useful for developers and QA testers who need to document a bug or show a layout problem in a specific browser version. The annotation tools are the point — a plain screenshot rarely explains what's wrong, while an arrow or a text label on the broken element does.

If you only need a local screenshot on your own machine, your operating system's built-in capture tool is faster. Browserling's advantage is capturing a remote browser session on a platform or browser version you don't have installed. For a broader look at cross-browser capture tools, see Browserling.

Next step

Open a session at a browser version you actually need to test, resize to the viewport you care about, then capture and annotate.

Is there a way to simulate different screen sizes for responsive design testing on catonmat.net?

Yes — but not as a design tool on catonmat.net itself. The relevant capability lives in Browserling, the browser-testing service whose new interface is described on catonmat.net. The post's "Display options" feature explicitly supports zooming the browser and changing the resolution to a larger or smaller one, and the page states this lets you do responsive web testing by seeing how a website looks at various screen sizes.

How it fits a responsive-testing workflow

For a concrete scenario: you have built a page and want to check it at a narrow mobile width, a mid-size tablet width, and a wide desktop width without switching physical devices. You would open the site in a Browserling browser session, use the display options to adjust resolution and zoom, and observe the layout at each size.

  • Resolution changes approximate different viewport sizes, which is the core of responsive checking.
  • Zoom helps on high-density displays, such as a 4K monitor, where the browser may otherwise render uncomfortably small.
  • Screen capture pairs with this: you can capture a region of the session and annotate it with a pen, rectangle, text, or eraser, which is handy for sharing a layout issue with a developer or client.

What to keep in mind

The page describes resolution and zoom controls, not a named device-preset list, so treat it as manual viewport testing rather than a drop-in replacement for a device-emulation panel. If you need precise breakpoint debugging, browser developer tools or a dedicated responsive-design checker may give finer control; Browserling's strength here is testing real browser and platform combinations at chosen sizes. For a quick cross-browser sanity check of a layout at several widths, the display options described on catonmat.net are a practical route.

Next step: open a session in the browser you care about and step through your site at your three or four key breakpoints, capturing annotated screenshots of anything that breaks. For related reading on the same site, see catonmat.net.

Can I share a live browser session with someone else using catonmat.net?

Yes. The page evidence for catonmat.net describes a "share a browser" feature in the Browserling interface that "allows sending a quick link to the current browser and website you're viewing." So rather than describing a screen recording or a static screenshot, the site presents this as a way to hand someone a link into the same browser session you have open.

H3 How it fits into a real workflow A common case: you're testing a checkout flow and hit a bug only you can reproduce. Instead of writing a long description ("click the third tab, then resize the window"), you'd send the link so the other person sees the same browser and page. The same applies to pairing with a developer, walking a client through a layout, or showing a colleague a responsive breakpoint you're questioning.

H3 Things to consider before relying on it

  • It is a link, not a co-editing tool. The evidence says it sends a quick link to the current browser and website. It doesn't state that two people can control the browser at once, so treat it as a hand-off or a shared view rather than Google-Docs-style collaboration.
  • Session lifetime matters. A quick link is convenient precisely because it's low-friction, but links like this are often time-limited or tied to the session. If the other person needs to keep working after you close the tab, check whether the browser stays alive.
  • Sensitive pages. If the session is logged into a staging account, an internal admin panel, or anything with customer data, sharing the link shares that access. Prefer a test account, and revoke or close the session when you're done.
  • Related features on the same page. The interface also lists screen capture with annotation tools, local testing via an SSH tunnel to localhost, and an on-screen keyboard, which cover adjacent needs: capture for async feedback, sharing for live feedback.

H3 Practical next step Open the browser and page you want to share, then look for the share option in the menu's feature area and copy the link it produces. Before sending it, open the link yourself in a private window while logged out, so you see exactly what the recipient will get. If the recipient needs to keep the session after you leave, confirm that first; if they only need to see a specific state, a screenshot from the capture feature may be the safer choice.

Related questions

More questions →
How to Use Browserling's Screen Capture and Annotation Feature

Browserling's screen capture feature lets you take a screenshot of any region of a remote browser session, then annotate it with a pen, rectangle, text, or eraser tool. You reach it through the new unified menu, which groups screen capture with other popular features below the platform, browser, and URL controls. The workflow is: open a browser session, select the region you want, edit the resulting screenshot, and copy it out. The steps below follow the feature as described in catonmat.net's announcement of Browserling's new user interface.

Step 1: Open a browser session

Screen capture works on a live Browserling session, so you first need a browser running.

  1. Open the menu and pick your operating system and browser version from the platform and browser selectors. The announcement notes this takes "a click or two" to load the version you need.
  2. Enter the address of the site you want to test in the URL navigation field and click the go button. A browser opens and loads that site.

If you want to follow along with the same page the announcement used, the quick link browserling.com/chrome/110/catonmat.net/new-browserling-ui opens that blog post in Chrome 110.

Step 2: Capture a region of the screen

  1. Open the menu and select Capture screen from the feature list at the bottom.
  2. Select the browser region you want to capture.

Once you select the region, Browserling opens a screenshot of that region and presents the editing tools. This is the point where the capture becomes an editable image rather than a live page.

Step 3: Annotate the screenshot

The editor gives you four tools:

Tool What it's for
Pen Freehand drawing or circling something on the page
Rectangle Boxing off an element or area you want to call out
Text annotation Adding a written note directly on the screenshot
Eraser Removing parts of your annotations

Use these to mark up layout bugs, highlight a specific element, or leave notes for whoever receives the screenshot.

Step 4: Get the screenshot out

The announcement states you can quickly copy screenshots to the clipboard, and that the feature has additional capabilities beyond the four editing tools. That makes the copy-to-clipboard path the fastest way to move a capture into a bug report, chat message, or document without saving a file first.

Practical notes

  • Capture is region-based, not full-page by default. You choose the browser region you want, so you can grab just the part that matters instead of the whole viewport.
  • Screen capture sits alongside related testing features. The same menu section also holds display options (zoom and resolution changes for responsive testing), local testing via an SSH tunnel to localhost or your local network, an on-screen keyboard for non-English computers and mobile devices, share-a-browser links, and feedback. If your goal is checking how a site looks at different sizes, display options and capture screen are often used together.
  • The announcement promises a more detailed article on this feature. catonmat.net says a follow-up post will cover the screen capture feature's other capabilities in more depth, so treat the four tools above as the documented baseline rather than the full extent of what's available.

If you only need a quick annotated image of one part of a remote browser session, the four steps above are enough: open a session, capture a region, mark it up, copy it out.

What is catonmat.net?

catonmat.net is the personal blog of Peteris Krumins, and its most recent pinned post is an announcement of a new user interface for Browserling, the browser-testing service he co-founded. If you arrived here looking for programming articles, tool write-ups, or the Browserling product announcement, that is what the site currently leads with. The page evidence available covers the Browserling UI post in detail, so this article focuses on what that post describes and what it tells you about the site.

What the current pinned post covers

The post is titled "A new user interface for Browserling!" and describes a redesigned product interface that puts all browsers, platforms, and features behind a single menu. It includes a quick browsing link that opens the same blog post inside the latest version of Chrome via Browserling:

browserling.com/chrome/110/catonmat.net/new-browserling-ui

That link is a concrete example of how the service is meant to be used: you pick a browser and version, point it at a URL, and the site loads there.

The new menu, feature by feature

The post splits the menu into two areas. The top part handles platform, browser, and target website selection. The bottom part collects the most-used features.

Feature What it does
Display options Zoom the browser in and out, and change resolution
Screen capture Take screenshots and annotate them
Local testing Open an SSH tunnel to localhost or a local network
On-screen keyboard Type in English on non-English computers, and type on mobile devices
Share a browser Send a quick link to the current browser and website
Send feedback Submit feedback to the team

Operating system and browser selection

This part of the menu lists all available platforms and browsers. The post's claim is that a click or two loads the browser version you need, rather than requiring you to navigate separate pages per platform.

URL navigation

You enter the address of the website you want to test, click the go button, and a browser opens with that site loaded. This is the core loop of the product: choose an environment, then choose a destination.

Display options

Two capabilities are described. Zooming helps on high-density displays — the post calls out 4K screens specifically. Changing resolution supports responsive testing, so you can see how a site renders at different screen sizes.

Capture screen

You select the region of the browser you want, and a screenshot of that region opens with editing tools: pen, rectangle, text annotation, and eraser. The post notes that more detail on this feature is coming in a follow-up article, and mentions additional abilities such as copying screenshots to the clipboard.

What this tells you about the site

Two things are worth separating.

catonmat.net is a blog. The post is written in the first person by the site's author, refers to "my team and I," and is framed as an announcement on his own site. That is consistent with a personal blog that also serves as a channel for product news.

Browserling is the product being announced. The features above — cross-browser testing, resolution switching, SSH tunneling to localhost, screenshot annotation — are testing-workflow features, not general browsing conveniences. If you need to check how a page behaves in a specific browser version, or on a screen size you do not have on hand, that is the use case the post is aimed at.

Practical notes before you try it

  • The quick link in the post pins a specific browser version (Chrome 110). If you need a different version, use the operating system and browser selection instead of the link.
  • Local testing requires an SSH tunnel to your localhost or local network. That is a setup step on your side, not something the menu does for you.
  • The post does not state pricing, account requirements, or whether the new interface is available on every plan. Treat those as unconfirmed until you check the product itself.
  • The author says a more detailed article on screen capture is planned, so if annotation is the feature you care about, the current post is a summary rather than full documentation.

Where to go next

If your goal is to read programming and tooling articles, browse the blog's archive rather than the pinned post. If your goal is to test a site across browsers, start from the operating system and browser selection in the new menu, then use URL navigation to load your target. The pinned post itself is the best current description of the interface, and the follow-up on screen capture is the piece to watch for if that feature matters to your workflow.

How Browserling's Display Options Support Responsive Web Testing

Browserling's display options let you zoom the browser in and out and change the browser resolution to a larger or smaller size. Because you can resize the viewport on demand, you can see how a website looks at different screen sizes without leaving the browser session — which is exactly what responsive web testing requires. This applies to any site you open through Browserling's URL navigation field, and the zoom control is especially useful on a 4K monitor where default rendering can look very small.

What the display options actually do

According to the Browserling new-UI announcement on catonmat.net, the display options feature covers two distinct controls:

  • Zoom — scales the browser view in and out. The post specifically notes this is useful on a 4K screen.
  • Resolution — switches the browser to a bigger or smaller resolution.

The post frames the combination directly as a responsive testing aid: "this feature lets you do responsive web testing as you can see how your website looks on various screen sizes."

How to use it for responsive testing

  1. Open the site you want to test. Use the URL navigation field: enter the website address, click the go button, and a browser opens and loads the site.
  2. Pick your target platform and browser first. The operating system and browser selection area lets you load a specific browser version in a click or two, so your responsive check runs against the rendering engine you care about.
  3. Open the display options from the menu. The new interface puts platform, browser, and site selection at the top of the menu and popular features — including display options — at the bottom.
  4. Change the resolution to a larger or smaller size and observe how the layout reflows.
  5. Use zoom when you need to inspect detail rather than test layout — for example, on a 4K display where the default view is hard to read.

Expected result: the same page rendered at a different viewport size, so you can compare breakpoint behavior across sizes in one session.

Zoom vs. resolution: which to reach for

Control What it changes Best used for
Zoom Scale of the browser view Reading detail on high-DPI/4K screens
Resolution Viewport size Checking layout at different screen sizes

These are not interchangeable. Zooming changes how large things appear to you; changing resolution changes the size the page believes it is rendering into. For responsive testing, resolution is the control that matters, and zoom is a comfort setting.

Practical notes and limits

  • The display options live inside the same menu as screen capture, local testing, on-screen keyboard, share-a-browser, and feedback, so you can resize and then immediately capture a screenshot of the result. The screen capture feature lets you select a browser region and annotate it with a pen, rectangle, text, and eraser tools.
  • The source material describes the feature at the level of "bigger or smaller" resolution and zoom in/out; it does not list specific resolution values or preset device profiles, so plan on adjusting manually rather than selecting named device presets.
  • Responsive testing here means visual inspection at different sizes. Nothing in the described feature set reports breakpoints, CSS media queries, or layout metrics automatically.

If your goal is simply to confirm a page holds up across a few widths, the resolution control plus a screenshot for each size is enough. If you need device-accurate emulation with named presets, this feature as described won't cover that on its own.

What Are the New Features in Browserling's New User Interface?

Browserling's new interface consolidates access to all browsers, platforms, and features into a single menu. The menu is split into two zones: the top handles platform, browser, and website selection, while the bottom provides shortcuts to frequently used tools. You can try it immediately via a quick browsing link that opens the blog post in the latest Chrome version.

A Single Menu for Everything

The core change is structural. Instead of scattering controls across the page, the new menu gathers everything needed to work with Browserling browsers in one place.

  • Top section: platform, browser, and target website selection
  • Bottom section: quick access to the most popular features

This layout means you configure what you want to test at the top, then reach for tools at the bottom without leaving the menu.

Operating System and Browser Selection

The OS and browser picker gives you quick access to all available platforms and browsers. With a click or two, you load the exact browser version you need. This is the starting point for any test session — pick your target environment first, then move on to navigation and tooling.

URL Navigation

The URL navigation field lets you jump straight to the site you want to test. Enter the website address, click the go button, and a browser opens and loads that site. No separate setup step is required between choosing a browser and loading a page.

Display Options

Display options cover two related tasks:

  • Zooming the browser in and out — useful on high-resolution displays such as 4K screens
  • Changing resolution to a larger or smaller size

Because you can adjust resolution freely, this feature also supports responsive web testing: you can see how your site renders across different screen sizes without switching tools.

Capture Screen

The screen capture feature takes screenshots of your browsing sessions. The flow is:

  1. Select the browser region you want to capture
  2. The screenshot of that region opens
  3. Use the editing tools — pen, rectangle, text annotation, and eraser — to modify it

According to the announcement, this feature has additional capabilities beyond annotation, including copying screenshots to the clipboard. A more detailed article on screen capture was promised in a follow-up post.

Other Features in the Menu

Beyond display options and screen capture, the bottom of the menu includes:

Feature What it does
Local testing Opens an SSH tunnel to localhost or your local network to test local websites
On-screen keyboard Provides an English keyboard on non-English computers and a keyboard on mobile devices
Share a browser Sends a quick link to the current browser and website you're viewing
Send feedback Submits feedback directly from the interface

How to Try It

The announcement provides a direct link: browserling.com/chrome/110/catonmat.net/new-browserling-ui. Following it opens the blog post itself in the latest version of Chrome, letting you see the new interface in action. From there, you can explore the menu, switch platforms and browsers, and test the features described above.

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 2005, this domain has about 21 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 NameCheap, Inc., a widely used domain service provider. The domain uses the common .net extension, which is not an independent safety signal.

DNS and Email

MX records exist, but SPF, DKIM and DMARC were not detected. Protection against domain impersonation may be incomplete. Nameservers are provided by Namecheap, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. 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 checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. 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 identifies nginx without an exact version. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

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

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. Open Graph is partially configured; og:type is missing. Twitter Card metadata is configured. The title has 12 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSNamecheap
HostingAkamai Connected Cloud
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagCedar Knolls, New Jersey, United States Inferred 104.200.28.42

Registration details

RDAP / WHOIS

RegistrarNameCheap, Inc.
Registered2005-07-08
Expires2027-07-08
Domain statusclient transfer prohibited
Nameserversdns1.registrar-servers.com、dns2.registrar-servers.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Acatonmat.net104.200.28.42300—
MXcatonmat.netaspmx.l.google.com3001
MXcatonmat.netalt1.aspmx.l.google.com3005
MXcatonmat.netalt2.aspmx.l.google.com3005
MXcatonmat.netalt3.aspmx.l.google.com30010
MXcatonmat.netalt4.aspmx.l.google.com30010
NScatonmat.netdns1.registrar-servers.com1800—
NScatonmat.netdns2.registrar-servers.com1800—
TXTcatonmat.netahrefs-site-verification_500b1e404df1d7537f47ad84f94b3376aff3b8fc1f6cf2abfcd0f95b9835180e300—
TXTcatonmat.netgoogle-site-verification=aXAUFOiWFF_OiqrmlUrhZN1sqJf5tnuYdMDpuXc1w8w300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2
Negotiated protocolTLSv1.2
Certificate subjectwww.catonmat.net
IssuerLet's Encrypt
Valid until2026-11-23T22:24 · Remaining when checked: 49 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
servernginx

Identified technologies

jQuerynginx

Pages, Search and Sharing

User reviews (0)

  • No reviews yet.