JPKCom DB

Info Tools — Examples

Info Tools walkthroughs: browser data for bug reports, IP via curl, telling Windows 11 from 10, live viewport, clock offset, Modernizr and the JSON export.

Back to overview: Info Tools · Open the live tool: www.jpkc.com/tools/info/

This page shows Info Tools through concrete walkthroughs. Since the tool needs no input, the examples revolve around typical questions from development, operations, and privacy. What each tab and field means in detail is covered in the manual.

Example 1: Collect browser data for a bug report

Goal: quickly record which browser and system a bug shows up on.

  1. Open Info Tools. The At a glance card sums up in one line which browser, in which major version, runs on which operating system.
  2. Next to Browser and Operating system sits a small copy button each. Every click puts exactly that one value on the clipboard and replaces the previous one — so copy the values one after the other and paste each straight into your bug report.
  3. If you also need the full User-Agent string, it's in the Headers tab, in the User-Agent row. It's even easier via the /tools/info/ua endpoint: the browser then shows nothing but the string as plain text.

Result: browser, version and operating system are in your bug report, with the raw User-Agent right alongside. If you'd rather grab everything in one go, Copy as JSON puts the complete dataset on the clipboard (see Example 5). In Chromium browsers, version and OS come from the Client Hints and are therefore more precise than the User-Agent string — the Browser field tells you which source the tool used.

Example 2: Fetch your own IP via curl

Goal: get only the public IP address in a script or terminal — no HTML around it.

  1. Call the single-value endpoint, either as a query parameter or as a path.
  2. In the browser only the IP appears, as plain text. On the command line:
curl -s "https://www.jpkc.com/tools/info/?ip"
curl -s https://www.jpkc.com/tools/info/ip
MYIP=$(curl -s https://www.jpkc.com/tools/info/ip)

Result: the output is exactly one line with your IP (text/plain, ending in a line break), perfect for scripts; in the variable assignment the shell strips the line break for you. The same way, ua, accept, enc, lang, gpc, dnt, port and protocol each return their value. To see everything at once, use headers (every request header, one per line) or json:

curl -s https://www.jpkc.com/tools/info/headers
curl -s https://www.jpkc.com/tools/info/json

You'll also find the ready-made commands in the tool's API tab, each with a copy button.

Example 3: Check viewport and pixel ratio during a responsive test

Goal: find out the actual viewport size and pixel ratio the browser is currently rendering at.

  1. In Info Tools, open the Display tab.
  2. Drag the browser window to the width you want to test.
  3. Read Viewport, Layout width (without scrollbar) and Device pixel ratio.

Result: you see the real CSS pixels of the viewport and the DPR (e.g. 2x). The values change live while you drag the window — no reload needed. Layout width is the width without the scrollbar; the difference from the viewport explains why a media-query breakpoint sometimes kicks in a few pixels earlier or later than expected.

Example 4: Inspect GPU and web-feature support

Goal: check which graphics card the browser reports and whether a specific web feature is supported.

  1. Open the Capabilities tab and, in the WebGL / GPU section, read GPU renderer and GPU vendor.
  2. Further down, in HTML5 & CSS feature detection (Modernizr), find the matching group — CSS, JavaScript or Audio & Video, for instance.
  3. A green badge means supported, red means not. Under video and audio you'll find the individual codecs with the browser's answer ("probably", "maybe" or "no").

Result: you learn whether hardware acceleration runs on a real GPU, whether the target feature is available in the current browser, and which video formats it can play. Each group shows how many of its features are supported; the overall total sits at the top right. Note: for privacy, the browser may obfuscate the GPU name.

Example 5: Save the complete findings as JSON

Goal: archive or hand off a full snapshot of all values.

  1. Click Export as JSON at the top.
  2. The browser downloads a file named browser-info-<date>.json.
  3. Alternatively, use Copy as JSON to put the same dataset on the clipboard.

Result: the file contains everything — the server-side values including the header list as well as the client-side ones (summary, Client Hints, hostname, load times, display, media features, locale including clock offset, WebGL, Modernizr, permissions, storage, battery, navigator). The tool waits for the asynchronous values before exporting, and the file is generated locally in the browser. Cookie values are never in it; your IP and hostname are. Handy for capturing the state of a test device or giving a support team the full picture.

Example 6: Inspect your own fingerprint

Goal: see how distinctive your browser looks to the outside world.

  1. In the Navigator tab, look at Plugins and MIME types — if your browser reports only the built-in PDF viewer or nothing at all, it gives nothing individual away here.
  2. Walk through the table of navigator properties: language, platform, hardwareConcurrency, deviceMemory and the like are all traits that together form a fingerprint.
  3. Capabilities (GPU, Client Hints), Display, Media features and Locale & time round out the picture: GPU model, unusual resolutions, a rare time zone or uncommon system settings make you especially distinguishable.

Result: you get a sense of which combination of values makes you recognizable. This is exactly the data tracking services evaluate — here out in the open and readable by you. How to draw conclusions from it is in the tips & tricks.

Example 7: Windows 11 or Windows 10?

Goal: find out which Windows version a machine really runs — the User-Agent string can't tell them apart.

  1. Open Info Tools in Chrome or Edge.
  2. In At a glance, read Operating system: it says Windows 11 or Windows 10, followed by the platform version.
  3. To double-check, look at Platform version in the User-Agent Client Hints section of the Capabilities tab: from major version 13 upward the tool reports Windows 11.
  4. Open the same page in Firefox: there it reads "Windows 10 or 11", and a note explains that your browser doesn't send Client Hints.

Result: you know the actual Windows version — and see why User-Agent statistics can't separate Windows 10 from 11. macOS is similar: without Client Hints the tool shows "10.15.7 or later", because browsers freeze that version in the User-Agent.

Example 8: Check dark mode and reduced motion

Goal: verify that your system actually passes on the settings you switched for design testing.

  1. Open the Media features tab.
  2. In your operating system, switch to dark mode or turn on "reduce motion".
  3. Watch prefers-color-scheme flip to dark and prefers-reduced-motion to reduce.

Result: you know which values your CSS media queries really see in this browser. If a feature carries the "not supported" badge, your browser doesn't know it at all — a rule built on it will never apply there.

Example 9: Check your system clock

Goal: find out whether your device's clock is off — say, when certificate errors, expired one-time codes or timestamps don't add up.

  1. Open the Locale & time tab.
  2. Read Clock offset vs. server.

Result: "in sync (± n ms)" means all is well. If the clock is off, you'll see something like "2.3 s behind (± 40 ms)" — "behind" means your clock is slow, "ahead" that it's fast. The number in brackets is the measurement uncertainty (half the request's round trip). While you're in the same tab, check that Time zone and UTC offset now are right too.

More on the individual tabs is in the manual, strategic advice in the tips & tricks. To get started right away, open the tool.