JPKCom DB

Info Tools — Examples

Concrete Info Tools walkthroughs: grab the user agent, fetch your IP via curl, check the viewport, read GPU and Modernizr, export everything as JSON.

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 card means in detail is covered in the manual.

Example 1: Grab your own user agent for debugging

Goal: quickly copy the exact browser identification, e.g. for a bug report.

  1. Open Info Tools and scroll to the HTTP Headers card.
  2. Read the value under HTTP_USER_AGENT.
  3. Click the small copy button next to the label.

Result: the full user-agent string is on your clipboard, ready to paste into a ticket or email. Because this value is server-side, it's exactly what every other server sees about you too — ideal for making rendering problems reproducible.

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: https://www.jpkc.com/tools/info/?ip.
  2. In the browser only the IP appears as plain text. On the command line:
curl -s "https://www.jpkc.com/tools/info/?ip"

Result: the output is exactly one line with your IP (text/plain), perfect for scripts. The same way, ?agent, ?accept, ?enc, ?lang, ?dnt, ?port, and ?protocol each return their single value. These endpoints are deliberately minimal — they output only the respective header or connection value.

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. Drag the browser window to the width you want to test.
  2. In Info Tools, go to the Screen & Display card.
  3. Read Viewport Size (window.innerWidth/innerHeight) and Device Pixel Ratio.

Result: you see the real CSS pixels of the viewport and the DPR (e.g. 2x). This helps verify media-query breakpoints and understand why an image needs to be sharper on a Retina display. These values are client-side — they change live when you resize the window and reload the page.

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. Scroll to the WebGL / GPU Info card and read GPU Renderer and GPU Vendor.
  2. Continue to the HTML5 & CSS3 Capabilities card (via Modernizr 3.13.1).
  3. In the relevant category (e.g. CSS or ES5/ES6+), find the feature you're after — a green badge means supported, red means not.

Result: you learn whether, say, hardware acceleration runs on a real GPU and whether the target feature is available in the current browser. The card header also shows how many features are supported vs. not supported overall. 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 right.
  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 headers and connection data as well as the client-side values (screen, navigator, plugins, WebGL, network, battery, storage, permissions, performance, and the Modernizr features). It's generated locally in the browser. Handy for capturing the state of a test device or giving a support team full context.

Example 6: Inspect your own fingerprint

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

  1. Look at Browser Plugins and MIME Types — if they're empty, your browser already blocks fingerprinting here.
  2. Walk through Navigator Properties: language, platform, hardwareConcurrency, deviceMemory, and the like are all traits that together form a fingerprint.
  3. WebGL / GPU Info and Screen & Display round out the picture: GPU model and unusual resolutions 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.

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