Website profiles · Technology insights · Alternatives

screenstab.com

Turn ordinary screenshots into beautiful image assets in no time

No paid content found
Visit website
Profile views 8 Outbound visits 2 Normal
Screenstab Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2019
Hosting
Domeneshop ASInferred
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 Screenstab?

Screenstab is a web tool for turning ordinary screenshots into polished image assets. Instead of pasting a raw screen capture into a slide, document or social post, you run it through Screenstab to get a cleaner, more presentable result — the kind of visual you would normally need a design app to produce.

What it is good for

  • Product mockups and feature announcements where a plain screenshot looks unfinished
  • Tutorials and documentation that benefit from consistent, styled screen images
  • Marketing and social posts that need quick visuals without opening a full design suite
  • Anyone who takes screenshots often but does not want to learn complex editing software

How it fits into a workflow

The typical scenario: you capture a screen, upload or drop it into Screenstab, choose a treatment, and export an image you can place directly into your deck, blog post or store listing. The appeal is speed — it removes the manual steps of cropping, framing, adding backgrounds and shadows by hand.

What to check before committing

  • Output formats and resolution — confirm the exported file types and sizes match where you plan to publish.
  • Customisation depth — some tools offer a handful of presets, others allow fine control over background, padding and angle. Decide which you need.
  • Batch handling — if you process many screenshots, check whether you can do them in one pass.
  • Licensing for commercial use — relevant if the images go into paid marketing or client work.

If you only need an occasional tidy screenshot, a free preset-based tool is usually enough. If screenshots are a regular part of your publishing routine, weigh the time saved against any paid tier. A practical first step is to take one real screenshot you would actually use and run it through Screenstab to see whether the default output is close to what you had in mind — that tells you more than any feature list.

How can I turn a screenshot into a beautiful image asset?

Use a screenshot-to-asset tool to clean up the capture, place it in a styled scene, and export at the size you need. Screenstab is one option built around this exact task: turning ordinary screenshots into image assets quickly. The practical goal is not just cropping the image, but making it look intentional—like a designed product shot rather than a raw screen grab.

H3 What "beautiful" usually means here

  • Framing: adding a device or browser frame so the screenshot reads as a real interface.
  • Background: replacing a plain white or desktop background with a gradient, solid color, or scene.
  • Angle and shadow: a slight perspective tilt and soft shadow make a flat capture feel dimensional.
  • Consistency: using the same style across several screenshots so they work as a set.

H3 A practical workflow

  1. Take a clean screenshot: hide personal data, notifications, and stray tabs.
  2. Crop to the area you want to show, keeping the important controls visible.
  3. Apply a frame, background, and shadow style.
  4. Export at the resolution your destination needs—social post, slide deck, landing page, or app store listing.
  5. Reuse the same preset for related images so they match.

H3 Choosing based on your situation

  • You need one polished image fast: a dedicated tool like Screenstab is the shortest path.
  • You want full control and already use design software: Figma gives you reusable frames and components.
  • You only need a quick mockup inside a device: Mockuphone is a simple alternative for device framing.
  • You want a real browser-window look: BrowserFrame wraps captures in browser chrome.

The trade-off is speed versus control: preset tools get you a good result in minutes, while design software takes longer but lets you match an exact brand system. As a next step, decide where the image will appear first, then pick the export size and style to match that context.

Can I use Screenstab to create images for social media posts?

Yes. Screenstab is designed to turn ordinary screenshots into polished image assets, and social media posts are a natural fit for that workflow. You take a screenshot you already have — a chat thread, an app interface, a chart, a testimonial, a snippet of code — and restyle it so it looks intentional rather than raw.

H3 Practical uses for social posts

  • Product demos: show a clean app screen without the clutter of your desktop, tabs or notifications.
  • Testimonials and reviews: screenshot a nice comment and present it as a quote card.
  • Data and charts: lift a graph out of a dashboard and give it a shareable frame.
  • Announcements: turn a plain text screenshot into a graphic for a launch or update.
  • Carousels and stories: consistent styling across several screenshots helps a multi-slide post feel like one set.

H3 Who gets the most out of it

If you post screenshots often — founders, indie makers, designers, developer advocates, social media managers — the value is speed. You avoid rebuilding each screenshot in a full design tool just to add a background and shadow. If you only post images occasionally, or you need heavy custom illustration, a general design tool will give you more control.

H3 What to check before committing

  • Whether the output sizes match the platforms you post to (square, vertical, landscape).
  • Whether you can keep a consistent look across a series of posts.
  • Whether the export format and resolution hold up when a platform re-compresses your image.
  • Whether the styling options are enough for your brand, or whether you still need to finish in another editor.

A useful next step: take one screenshot you would actually post, run it through, and see whether the result is publish-ready without further editing. If it is, batch your next few posts the same way. For broader design work alongside it, tools such as Canva or Figma cover layouts and branding that a screenshot-focused tool is not built for.

What types of screenshots work best with Screenstab?

Screenstab works best with screenshots that have a clear, simple subject and a relatively clean background: app interfaces, UI components, dashboards, charts, code snippets, and plain browser or device mockups. These tend to convert into attractive image assets because the tool's purpose is to restyle ordinary screenshots into more polished visuals, and that restyling reads most clearly when the original image isn't visually crowded.

Less ideal are screenshots that are dense with small text, cluttered with overlapping windows, or heavy on photographic detail. For example, a full desktop screenshot with a dozen open panels gives the restyling little room to improve legibility, whereas a single settings panel or a product card screenshot holds up well.

H3 Practical test Before committing a batch, run one representative screenshot through and check whether text remains readable and the focal element still stands out. If it does, the same category of screenshot will likely work well; if not, crop to the essential region first.

A useful decision criterion is purpose: screenshots meant for marketing pages, social posts, or documentation headers benefit most, while screenshots meant for precise technical reference may be better left unprocessed. For general screenshot capture and annotation habits, see Screenstab.

How does Screenstab compare to other screenshot editing tools?

Screenstab is best understood as a screenshot beautifier rather than a general screenshot editor. Its stated purpose is turning ordinary screenshots into polished image assets — the kind of presentation-focused output you'd use in a portfolio, slide deck, blog post or app store listing. That places it closer to mockup and "screenshot-to-marketing-image" tools than to annotation-heavy editors.

Where the difference shows up

Task Screenstab's focus Typical screenshot editors
Making a screenshot look presentable in a post or slide Core purpose Possible, but usually manual
Adding arrows, boxes, numbered callouts Not the emphasis Core purpose
Blurring, redacting or cropping sensitive content Not the emphasis Common built-in feature
Capturing the screen itself Not the emphasis Often built in
Producing consistent branded visuals Likely the intended outcome Usually one-off, per-image work

Who each type suits

  • Screenstab-style tooling: designers, marketers, indie developers and writers who already have the screenshot and need it to look good fast — e.g. a Mac app window shown at an angle with a clean background for a landing page.
  • Annotation editors: support teams, QA testers, technical writers and bug reporters who need to point at a specific button, step number or error message.
  • Full screenshot utilities: people who need capture, scrolling capture, OCR or recording in one place.

Practical decision criteria

Ask three questions before choosing:

  1. Is the problem "it looks flat" or "it's unclear"? Looks → beautifier. Unclear → annotation editor.
  2. Do you need to hide anything? If yes, confirm the tool has blur or redaction before committing.
  3. Will you repeat this style across many images? Consistency favours a dedicated beautifier with saved presets over hand-editing each shot.

A concrete scenario

You ship a small desktop app and want six images for a Product Hunt launch. You capture the windows with your OS tool, then run them through Screenstab to get a uniform, presentable look — no arrows or labels needed because the captions do that job. For the help-centre article explaining the same app, you'd instead want an annotation-capable editor so you can circle the settings icon.

Next step

Open Screenstab with one real screenshot you need to publish, and run it through. If the result solves the "looks unpolished" problem in a couple of minutes, it fits your workflow; if you find yourself wishing for arrows, blur or cropping, pair it with a general editor rather than replacing it. For inspiration on the presentation side, see Dribbble and Behance, where this style of asset is common.

Is there a free version of Screenstab and what are its limitations?

Screenstab is a browser-based tool for turning plain screenshots into more polished image assets, and yes — it offers a free entry point. The free version is best understood as a way to test the workflow and produce occasional assets, not as a full production license.

What the free version gets you

  • Access to the core screenshot-to-asset conversion. You can upload a screenshot and get a styled result, which is the main thing the tool does.
  • A way to evaluate output quality before committing. This matters because the value of a tool like this depends on whether its treatments match your visual style.
  • No install or account friction implied by the browser workflow. You can try it in a session rather than setting up a desktop app.

Typical limitations to expect

  • Export restrictions. Free tiers in this category usually cap resolution, add a watermark, or limit file formats such as PNG versus SVG.
  • Usage caps. A set number of conversions per day or month, or a limited number of saved projects.
  • Fewer style options. Premium backgrounds, gradients, shadows, or device frames are often gated.
  • No commercial license on the free tier. If you are producing marketing images for a client or a paid product, check the terms before publishing.

Who should use which

Situation Free version Paid version
Testing whether the style fits your brand Good fit Unnecessary
One-off blog or slide image Usually fine, watch watermarks Cleaner output
Client work or paid ads Risky — check licensing Appropriate
High-volume or team use Too limited Appropriate

A practical next step

Take one real screenshot you actually need — a product UI shot for a landing page, say — and run it through the free tier first. Then judge two things: whether the default styling is close enough to your brand without heavy editing, and whether the export quality holds up at the size you need. If either fails, the paid tier is the question to investigate, not the free one.

Related questions

More questions →
What is Screenstab?

Screenstab is a web tool that turns ordinary screenshots into polished image assets. It is aimed at people who need presentable visuals quickly—such as marketers, bloggers, and product teams—without opening a full design suite. The site's own description states the core promise: "Turn ordinary screenshots into beautiful image assets in no time."

What problem it solves

Raw screenshots usually look flat and unpolished. They carry browser chrome, mismatched backgrounds, and awkward proportions that make them hard to drop into a landing page, slide deck, or social post. Screenstab targets that gap: instead of manually cropping, masking, and styling each capture in a design tool, you feed in a screenshot and get back something that looks intentionally designed.

Who it is for

  • Content and marketing teams that publish product screenshots regularly and want a consistent look.
  • Bloggers and newsletter writers who need a clean visual but do not have a designer on hand.
  • Founders and indie makers assembling a landing page or pitch deck from app captures.
  • Anyone who wants a screenshot to read as a finished asset rather than a raw grab.

How it differs from alternatives

Approach Typical effort Result
OS screenshot tool One keystroke Raw capture, no styling
Full design software Manual masking, backgrounds, shadows Full control, higher time cost
Screenstab Upload and process Styled asset with minimal manual work

The distinction is scope. A screenshot tool stops at capture; design software starts from a blank canvas and expects you to build the presentation yourself. Screenstab sits between them, handling the styling step so the screenshot itself becomes the finished asset.

What to keep in mind

The available site information confirms the purpose and positioning but does not detail specific features, output formats, or pricing. If your decision depends on those specifics, check the site directly rather than assuming capabilities. For a quick task—say, turning an app screenshot into something you can drop into a blog post—the tool is worth trying first, since the value proposition is speed rather than deep customization.

How Is Screenstab Different from Taking a Regular Screenshot?

A regular screenshot captures exactly what is on your screen and is meant to be used as-is. Screenstab, based on its own description, is built to "turn ordinary screenshots into beautiful image assets in no time" — so the input may start as a screenshot, but the output is a designed asset rather than a raw capture. The difference is one of purpose: a screenshot is a record, while a Screenstab asset is a presentation-ready image.

The core difference in one table

Dimension Regular screenshot Screenstab
Primary goal Record what is on screen Produce a beautiful image asset
Typical output A raw, literal capture A polished, presentable image
Effort after capture Usually none — you use it directly The tool handles the transformation
Speed emphasis Instant by nature "In no time," per the site description
Best fit Documentation, bug reports, quick sharing Marketing visuals, portfolios, social posts, product pages

What "turning a screenshot into an image asset" means

A screenshot is a faithful copy: every pixel matches your display, including browser chrome, desktop clutter, and awkward framing. An image asset is something you would actually put in front of an audience — a clean, attractive visual that fits a slide, a landing page, or a post.

Screenstab sits on the second side of that line. Its stated promise is speed and beauty: you bring an ordinary screenshot, and the result is something presentable without a full design workflow.

When a regular screenshot is still the better choice

  • You need an exact, verifiable record — support tickets, step-by-step instructions, compliance evidence.
  • The content matters more than the presentation.
  • You want zero processing and zero dependency on another tool.

When Screenstab is the better fit

  • The screenshot is going in front of customers, readers, or an audience.
  • You want a polished look but don't want to open a full design tool.
  • You have several screenshots to turn into consistent visuals quickly.

A practical way to decide

Ask one question: is this image meant to be evidence or to be seen? If it's evidence, take the screenshot and use it directly. If it's meant to be seen — a hero image, a feature highlight, a portfolio piece — start from the screenshot and let Screenstab do the conversion, since that transformation is the entire point of the tool.

One caveat worth noting: the available site information describes the goal ("beautiful image assets," "in no time") but does not detail specific editing features or technical steps. If your decision depends on a particular effect or export format, check the site directly before committing.

What It Means to Turn Screenshots into Image Assets on Screenstab

Screenstab is a tool that takes an ordinary screenshot and turns it into a styled image asset — a picture you can drop into a presentation, a social post, or a product page without it looking like a raw screen capture. The core idea is presentational: the content of your screenshot stays the same, but the way it is framed and displayed changes so it reads as a designed visual rather than a plain grab of your screen. This is useful whenever a screenshot needs to look intentional rather than incidental.

What "image asset" means here

An image asset is a finished picture you can reuse. In this context it is not a file format claim or an editing suite — it is the output of a styling step applied to a screenshot. Practically, that means:

  • The screenshot is treated as the subject, not the final product.
  • The result is meant to be placed somewhere: a slide, a landing page, a chat message, a portfolio.
  • The value comes from presentation, not from adding new information to the image.

So "turning a screenshot into an image asset" describes a shift in purpose. You stop sharing a capture of your screen and start sharing a visual that happens to contain screen content.

How a styled screenshot differs from a raw one

A raw screenshot carries the visual language of the operating system: hard edges, a flat rectangle, whatever background was behind the window, and often a cursor or notification. A styled asset usually changes the framing around that content. Common differences include:

Aspect Raw screenshot Styled image asset
Edges Sharp, unmodified Often rounded or softened
Background Whatever was on screen Usually clean or neutral
Depth Flat May sit on a surface or cast a shadow
Intent "Here is my screen" "Here is a designed visual"

The content is identical. What changes is whether the image looks like evidence or like a deliberate piece of design.

Where this is useful

The main use cases follow directly from the difference above — anywhere a plain screenshot would look unfinished:

  • Presentations and demos — showing an app or interface without the surrounding desktop clutter.
  • Social media — a screenshot posted as-is often reads as low effort; a framed version reads as content.
  • Product and marketing pages — interface shots that need to sit on a page background without a visible seam.
  • Documentation and tutorials — consistent framing across many screenshots so a series looks like one set.

In each case the requirement is the same: the screenshot must be recognizable as a screenshot, but presented so it fits the surrounding design.

What to check before relying on it

Because the source material here describes the purpose rather than a feature list, treat the following as conditions to verify against the actual tool rather than assumptions:

  • Whether the styling is applied automatically or requires manual adjustment.
  • Whether the output keeps the original resolution, since a styled asset that is scaled down may not suit high-resolution displays.
  • Whether you can control the background and framing, or whether you get a fixed look.
  • Whether there are limits on how many images you can process, and under what terms.

If your goal is simply to make a screenshot look presentable in a slide or post, the concept fits. If your goal is to edit the content inside the screenshot, that is a different task and outside what "turning a screenshot into an image asset" describes.

Who Can Benefit from Using Screenstab?

Screenstab is for anyone who regularly shares screenshots and wants them to look like deliberate design assets rather than raw captures. According to the site, it turns "ordinary screenshots into beautiful image assets in no time." If your work involves presenting, publishing, or pitching screens, and the screenshot itself is the visual, you're in the target group. If you need full layout control or a complete design suite, it's the wrong tool.

The core problem it addresses

A plain screenshot carries visual noise: browser chrome, desktop clutter, inconsistent backgrounds, and a flat, unedited look. That's fine for a bug report, but weak for a landing page, a slide deck, a social post, or a client deliverable. Screenstab's promise is speed — you feed in a screenshot and get back something presentable, without opening a design tool and rebuilding the frame by hand.

Who gets the most out of it

Content creators and marketers

If you publish tutorials, product walkthroughs, comparison posts, or social carousels, screenshots are a recurring asset. The bottleneck usually isn't the capture, it's making each one look consistent and intentional. A tool that converts screenshots into styled assets in one pass removes that per-image fiddling.

Designers who need quick mockup visuals

Designers rarely need help with final polish, but they often need fast placeholder or presentation imagery — showing a UI in context during a review, a spec, or a portfolio draft. Screenstab fits the "good enough, right now" slot rather than the "final production asset" slot.

Founders, PMs, and anyone pitching

Demo decks, investor updates, and internal proposals all lean on screenshots of the product. When the screenshot is doing persuasion work, presentation quality matters. This is a low-effort way to raise that quality without a design request.

Support, docs, and community teams

Help articles and onboarding docs benefit from screens that look clean and framed rather than pasted in raw. Consistency across many screenshots is the real win here.

Who should look elsewhere

  • You need pixel-level control. If you must match a brand system exactly, place elements precisely, or export layered files, a general design tool is the better fit.
  • Your screenshots are data, not visuals. Charts, logs, and error dumps usually don't need beautification.
  • You only produce screenshots occasionally. The setup and learning cost may not pay off if it's a once-a-quarter task.
  • You need video or motion. The site's stated scope is image assets from screenshots.

How to decide

Your situation Screenstab is likely…
Frequent screenshots for public-facing content A good fit
Need speed over fine control A good fit
Need exact brand or layout control Not the right tool
Screenshots are internal or diagnostic Unnecessary
Occasional one-off use Marginal

A practical test: take one screenshot you'd normally publish as-is and run it through. If the result is something you'd ship without further editing, it fits your workflow. If you immediately want to move elements around, you've outgrown it for that task.

What to verify before committing

The site describes the capability but the supplied page material doesn't state pricing, account requirements, export formats, or resolution limits. Check those directly on screenstab.com before adopting it — particularly whether you can export at the sizes your channels need, and whether there's a free tier or trial to test with your own screenshots first.

How to Get Started with Screenstab

Screenstab is a web tool at screenstab.com that turns ordinary screenshots into polished image assets. To get started, go to the site, prepare the screenshots you want to convert, and follow the on-screen guidance for uploading or importing them. The exact sign-up, pricing, and export steps aren't confirmed in the available site information, so treat those as things to verify directly on the page rather than assume.

What Screenstab Does

According to its own description, Screenstab is built to "turn ordinary screenshots into beautiful image assets in no time." That places it in the category of screenshot-to-asset converters: you bring a screenshot, and the tool produces a more presentable image you can use elsewhere (for example, in a presentation, a landing page, or a product mockup).

The practical takeaway: the input is a screenshot, and the output is a styled image asset. Everything between those two points happens on the site.

Before You Start: What to Prepare

Because the tool's core input is a screenshot, the most useful preparation is on your side:

  • A screenshot you actually want to use. Capture it at the highest resolution your device allows, since a low-resolution source limits how good the final asset can look.
  • A clean capture. Close or hide anything you don't want visible (notifications, personal tabs, unrelated windows) before taking the shot.
  • A sense of the destination. Knowing whether the asset is for a slide, a website, or a mockup helps you judge whether the result looks right.

Steps to Get Started

  1. Open screenstab.com in your browser. This is the entry point for the tool.
  2. Look for the upload or import option. The site's purpose is converting screenshots, so the primary action is expected to be bringing an image in. Use whatever upload control the page presents.
  3. Select your screenshot from your device and confirm the import.
  4. Review the result the tool produces and adjust using any controls the page offers.
  5. Check the site's own instructions and examples. Screenstab's page is the authoritative source for how its workflow behaves, including any steps beyond the initial import.

If a step above doesn't match what you see, follow the site's interface rather than this outline — the page is the source of truth.

What Isn't Confirmed

The available site information does not specify:

  • Whether an account or sign-up is required
  • Whether there is a free tier, paid plan, or usage limit
  • Which file formats are accepted
  • How finished assets are exported or downloaded

Don't assume any of these are free, unlimited, or account-free. Confirm them on the site itself before relying on the tool for a project with a deadline.

Common Snags to Expect

  • Low-quality source screenshots tend to produce weak results no matter how good the styling is. Start with a sharp capture.
  • Cluttered screenshots carry unwanted content into the final asset. Clean the capture first.
  • Assuming a workflow that isn't shown. If you can't find an upload button, export option, or account page, it may simply not exist yet — check the site's visible guidance instead of guessing at hidden menus.

Bottom Line

Start at screenstab.com, bring a clean, high-resolution screenshot, and follow the site's own prompts for importing and converting it. Verify account, pricing, format, and export details on the page, since those specifics aren't established in the information available here.

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 2019, this domain has about 7 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 domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by hyp.net, indicating managed DNS hosting. MX records point to the domeneshop.no email service. DNSSEC is enabled, allowing validating resolvers to authenticate signed DNS data. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

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 response lacks these common security headers: HSTS, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. 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.

Technology Stack Analysis

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

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. Open Graph is partially configured; og:title, og:description, og:type is missing. The title has 10 characters, within a common display range. A meta description is present, with 64 characters. The observed directives allow indexing and link following.

Hosting and Email

DNShyp.net
HostingDomeneshop AS
Emaildomeneshop.no
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Norway flagNorway Inferred 194.63.249.212

Registration details

RDAP / WHOIS

RegistrarDomeneshop AS dba domainnameshop.com
Registered2019-06-11
Expires2027-06-11
Domain statusclient transfer prohibited
Nameserversns1.hyp.net、ns2.hyp.net、ns3.hyp.net
DNSSECsigned

DNS records

DNS

TypeNameValueTTLPriority
Awww.screenstab.com194.63.249.2123600—
AAAAwww.screenstab.com2a01:5b40:0:4a01:0:bbbf:ee69:6d663600—
MXscreenstab.commx.domeneshop.no360010
NSscreenstab.comns1.hyp.net86400—
NSscreenstab.comns2.hyp.net86400—
NSscreenstab.comns3.hyp.net86400—
TXTscreenstab.comv=spf1 include:_spf.domeneshop.no ~all3600—
DSscreenstab.com55032 15 2 c215ea0c535803a504fcd20984695fbe39732bb801f185b0d84cea8326f4c1a586400—
DSscreenstab.com55032 15 4 c9b79488839d0be39dd20a8d2f8a981ec289ab908d80c52402d1096e6037a13479f4299be1eb63b8fa87a379e24c3e6f86400—
DMARC_dmarc.screenstab.comv=DMARC1; p=quarantine; rua=mailto:[email protected]3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.screenstab.com
IssuerLet's Encrypt
Valid until2026-12-10T02:49 · Remaining when checked: 66 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
servernginx
content-security-policyupgrade-insecure-requests
access-control-allow-origin*

Identified technologies

Sentrynginx

Pages, Search and Sharing

User reviews (0)

  • No reviews yet.