Website profiles · Technology insights · Alternatives

slemma.com

Paid content
Visit website
Profile views 8 Outbound visits 2 Normal
Business Intelligence by Slemma | Analytics and Dashboard Software Full homepage screenshot

At a glance

Category
Data & Analytics
Language
English
Paid-content signal
Paid contentObserved
Registered
2015
Hosting
Amazon.com, Inc.Inferred
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 Slemma?

Slemma is a business intelligence and dashboard platform: it connects to data sources, lets you assemble charts and dashboards, and shares the results with others. It is aimed at teams that want reporting without building a custom analytics stack, and it is commonly listed among tools such as Tableau and Microsoft Power BI when teams compare options.

What it is used for

  • Dashboards and reporting: combining data from multiple sources into a single view for recurring business reporting.
  • Self-service analysis: letting analysts or business users explore data and build charts without engineering work for each request.
  • Sharing results: distributing dashboards to colleagues, clients or stakeholders.

Who it suits

Small and mid-sized teams, agencies and departments that need fast, shareable reporting and do not want to maintain a warehouse-first setup. Larger organisations with strict governance or very complex data models may find a dedicated enterprise BI platform a better fit.

Trade-offs to weigh

Slemma's pitch is convenience: connect, visualise, share. The cost of that convenience is less control over data modelling and infrastructure than a self-managed stack gives you. If your reporting needs are mostly standard charts over common SaaS or database sources, that trade-off is usually fine. If you need heavy transformation, custom governance or embedded analytics at scale, evaluate the depth of those features first.

Next step

Open the pricing page at Slemma to check plan limits such as data sources, users and refresh frequency, then run a short trial against one real dataset your team already reports on manually. If it replaces that manual work in an afternoon, it is likely a good fit; if you spend the trial fighting connectors or modelling, look at alternatives.

How does Slemma's free trial work and what are the pricing tiers?

Slemma's pricing page is the authoritative source for what its free trial includes and which tiers exist, because the product itself is a JavaScript application that renders no plan details in static page text. That means you should open Slemma directly and check its Pricing page rather than relying on second-hand summaries, which often quote outdated seat limits or feature gates.

How to evaluate the trial

Treat the trial as a fit test, not a full rollout. A practical approach:

  • Confirm the trial length and whether it requires a credit card before you invite colleagues.
  • Identify which connectors you actually need (for example, a SQL warehouse, a spreadsheet source, or a marketing platform) and test those first, since connector coverage is usually where trials succeed or fail.
  • Build one dashboard that mirrors a real weekly report you already produce, then time how long it takes. That single exercise reveals more than browsing feature lists.
  • Check what happens to your dashboards and data sources when the trial ends, including whether they are retained, exported, or deleted.

Reading the pricing tiers

Slemma's tiers are typically structured along three axes: number of users or seats, number of data sources or connectors, and whether scheduled refresh and sharing are included. When comparing plans on the site, ask:

  • Does the entry tier allow scheduled refreshes, or only manual ones? Manual refresh is fine for a one-off analysis but not for an operations dashboard.
  • Are viewer seats cheaper than editor seats? If most of your audience only consumes dashboards, a plan that separates these roles can be far less expensive.
  • Is there a per-source limit? Teams with many small data sources hit this faster than teams with one large warehouse.

Who each tier tends to suit

A solo analyst or a small team prototyping a single dashboard usually fits the lowest paid tier, provided scheduled refresh is included. A department running shared reporting for multiple stakeholders needs a tier with role-based access and more connectors. Enterprise buyers should look for SSO, audit controls, and a named support contact, since those are the features that justify the jump in price rather than dashboard count.

Your next step: open the Pricing page, note the exact trial duration and the seat and connector limits of each tier, then map those numbers against your own list of data sources and dashboard viewers before starting the clock.

Can I connect Slemma to databases or data warehouses like SQL, Google Analytics, or Salesforce?

Yes. Slemma is built to pull data from external sources rather than requiring you to upload flat files, and its connector set covers the three categories you named: relational databases, web analytics, and CRM platforms.

What that looks like in practice

  • SQL databases and warehouses: Slemma connects to SQL-based sources, so a data warehouse or production database can be queried directly and its tables used as the basis for charts and dashboards.
  • Google Analytics: GA is a supported source, which means traffic, acquisition and conversion metrics can sit on the same dashboard as revenue or pipeline data.
  • Salesforce: Salesforce is also supported, so opportunities, accounts and pipeline stages can be blended with other business data.

Who benefits most

A marketing analyst who wants to show paid traffic next to closed-won revenue, or an operations lead who wants warehouse order data beside CRM pipeline, gets the most value. The point of connecting several sources is that you avoid exporting CSVs and reconciling them by hand each week.

Choosing between connectors and file uploads

Approach Best when Trade-off
Live database/warehouse connection Data changes often and you want current numbers Needs query access and someone who understands the schema
SaaS connectors (Google Analytics, Salesforce) You want standard metrics without writing queries Limited to the fields and granularity the connector exposes
Manual file upload One-off analysis or a source with no connector Goes stale immediately and doesn't refresh

A practical next step: list the two or three questions your dashboard must answer, then check whether each required field is actually exposed by the relevant connector. Connector availability is only half the test; field-level access is what determines whether the dashboard works.

How do I build an interactive dashboard in Slemma without coding?

Slemma is built for exactly this: connecting data sources and assembling charts into a shared dashboard through a visual interface rather than scripts. The typical path is to connect a source, pick a dataset, drag fields onto a chart, then arrange those charts on a dashboard canvas and share it. Because the product's public page loads as a JavaScript app, treat the exact menu names and steps below as the general shape of the workflow and confirm the current wording after you sign in.

A practical build order

  1. Connect one source first. Start with a single dataset you already understand — a spreadsheet, a database table, or a marketing/analytics account. Mixing sources before your first chart works adds complexity you don't need yet.
  2. Choose a chart type that matches the question. Trends over time → line or area. Comparison across categories → bar. Composition → stacked bar or pie (only with few slices). Single current value → a number/KPI tile.
  3. Drag fields into the chart's shelves. Dimensions (categories, dates) go on the grouping axis; measures (numbers) go on the value axis. Aggregation — sum, average, count — is usually a dropdown on the measure.
  4. Add filters and a date range. These are what make a dashboard "interactive" rather than a static report. A date control plus one or two category filters covers most needs.
  5. Arrange the canvas. Put the headline KPIs top-left, trend charts next, and detail tables lower. Keep it to one screen where possible.
  6. Share with the right permission level. Viewers who only need to read should not get edit rights; editors who maintain the data should.

Where people get stuck

  • Grain mismatch. If one dataset is daily and another is per-order, joining them produces inflated totals. Decide the grain before you combine anything.
  • Too many charts. A dashboard answering five questions well beats one answering twenty badly. If a chart doesn't change a decision, cut it.
  • Filters that don't propagate. Check whether a filter applies to the whole dashboard or just one chart — this is the most common source of "why don't the numbers match?" confusion.

Choosing between tools

If you need… Look for…
Fast setup from spreadsheets and cloud apps A connector-first BI tool with a drag-and-drop canvas
Heavy data modeling and SQL control A tool that exposes the query layer
Dashboards embedded in your own product Embedding support and viewer-level permissions

For a broader comparison, Looker and Tableau are the usual enterprise references, while Metabase and Mode are worth a look if your team is comfortable with SQL. Slemma sits in the visual, no-code camp, so it suits analysts and operations staff who want a working dashboard today rather than a modeled semantic layer.

Next step: before building anything, write down the three questions the dashboard must answer and who will read it. Then connect one source and build a single chart that answers question one. If that chart is easy to produce and the numbers are trustworthy, the rest of the dashboard is mostly repetition. Slemma offers a free trial and publishes pricing at Slemma, so you can test the workflow against your own data before committing.

Is Slemma suitable for embedding dashboards into my own application or website?

Yes—Slemma is designed with embedding in mind, so it can work for putting dashboards inside your own product or site. The page evidence for slemma.com is thin (it only shows a JavaScript app shell), so the embedding specifics below should be treated as general capabilities to verify on Slemma rather than confirmed feature details.

What embedding usually involves

Most BI tools that support embedding give you one of two paths:

  • White-label embedding: dashboards appear as a native part of your application, with your branding and access controls, often via an iframe or JavaScript SDK.
  • Public or shareable links: a simpler option where you drop a link or iframe into a page, but with less control over authentication and styling.

Slemma positions itself as analytics and dashboard software with an embed use case, so it fits teams that want to surface charts and KPIs directly to end users rather than sending them to a separate BI portal.

Who this suits

  • SaaS product teams adding an analytics tab or customer-facing reporting.
  • Agencies delivering branded dashboards to clients.
  • Internal tools where non-technical staff need live data without leaving the app.

If your users need row-level security, per-tenant data isolation, or a fully custom look, confirm those before committing.

Decision criteria

Ask these questions when evaluating Slemma against alternatives:

  1. Does the embed support the authentication model you already use (SSO, tokens, signed URLs)?
  2. Can you theme it to match your UI, or will it look like a third-party widget?
  3. How are data refreshes and query costs handled per embedded view?
  4. Is there a free trial so you can test the embed in a staging environment?

A practical next step: request the free trial, embed one dashboard into a test page, and check how it behaves under your real login flow. For comparison, established embedding options include Looker, Tableau, and Metabase, each with different trade-offs in cost, customization, and developer effort.

What are the main differences between Slemma and other business intelligence tools like Tableau or Power BI?

Slemma is a browser-based business intelligence and dashboard tool, while Tableau and Power BI are broader analytics platforms with much larger ecosystems. The practical difference is less about chart types and more about how much setup, governance, and data modeling each tool expects from you.

How they tend to differ in practice

  • Deployment model: Slemma is delivered as a web app, so you open it in a browser and connect data rather than install a desktop authoring client. Tableau has a strong desktop authoring tradition alongside its cloud products; Power BI is built around a Windows desktop authoring app plus a cloud service.
  • Data preparation depth: Power BI and Tableau offer mature, separate data-prep layers (Power Query and Tableau Prep, respectively) for shaping messy data before visualization. Slemma is more oriented toward connecting to a source and building dashboards directly, which is faster for clean, well-structured data and more limiting when you need heavy transformation.
  • Ecosystem and community: Tableau and Power BI have extensive marketplaces, templates, certification paths, and large user communities. Slemma's ecosystem is smaller, so you will rely more on its built-in connectors and your own templates.
  • Cost and licensing complexity: All three offer free trials, and Slemma publishes a pricing page at Slemma. Tableau and Power BI have multiple tiers and per-user models that can become complex at scale, so compare total cost across your actual viewer and author counts rather than list prices alone.
  • Best-fit audience: Slemma suits small to mid-sized teams that want shareable dashboards without a dedicated BI developer. Tableau and Power BI suit organizations that need governed semantic models, row-level security, and a wide range of enterprise data sources.

A concrete way to decide

Start with your messiest data source and your least technical dashboard author. If that person can connect the source and publish a useful dashboard in Slemma without help, it is likely a good fit. If your data requires significant cleaning, or you need strict governance and a large connector library, one of the bigger platforms will usually save time later.

For comparison, you can review official feature and pricing information at Tableau and Power BI.

Related questions

More questions →
What to Consider When Comparing Slemma With Other BI Tools

Slemma is a business intelligence and dashboard tool whose public site (slemma.com) is a JavaScript app, so the only page evidence available is the app shell plus a pricing link at /plans-pricing and signals for "free trial" and "pricing." That means you should treat Slemma as one candidate in a shortlist and verify current capabilities and plan terms directly on its pricing page before deciding. The four dimensions below are the ones that actually change the answer: data connections, dashboard and visualization depth, pricing and trial conditions, and collaboration plus the skill level your team needs.

Data source connections and integration

This is usually the first filter, because a BI tool is only as useful as the data it can reach.

  • List every source you need now: warehouses (for example BigQuery, Redshift, Snowflake), SaaS apps (for example Google Analytics, Salesforce, HubSpot), flat files (CSV/Excel), and internal databases.
  • For each source, check whether the connection is native, API-based, or requires a third-party connector or middleware.
  • Check refresh behavior: scheduled refresh, manual refresh, or live query. A dashboard that only updates daily is fine for weekly reporting and wrong for operational monitoring.
  • Check whether you can transform or join data inside the tool, or whether you must prepare it upstream.

Slemma is positioned as an analytics and dashboard product, so the practical question is whether it natively covers your specific stack. Because the site content is not readable without JavaScript, confirm the connector list on the live app or pricing page rather than assuming coverage.

Dashboards and visualization

Compare tools on the same sample task so the comparison is fair. For example, take one real question — "monthly revenue by region versus target" — and try to build it in each tool.

  • Chart types: do you get the charts you actually use (time series, bar, scatter, funnel, map, pivot table)?
  • Calculated fields: can you write formulas or custom SQL, or are you limited to pre-built aggregations?
  • Interactivity: filters, drill-down, cross-filtering between charts, and parameters.
  • Layout and embedding: can you share a public link, embed in an app, or export to PDF/CSV?
  • Performance at your data volume: a tool that is fast on 10,000 rows may stall on 10 million.

If your reporting is mostly standard KPI dashboards, most tools in this category will look similar. The differences show up in custom calculations, embedding, and how much manual formatting you have to do.

Pricing and trial conditions

Slemma's site signals a free trial and a dedicated pricing page, but the actual numbers are not in the available page evidence, so do not assume a free tier or a specific price.

When comparing, normalize plans to the same unit:

What to check Why it matters
Price per user vs. per account Per-seat pricing scales badly for viewer-heavy teams
Viewer vs. editor seats Many tools charge only for editors, which changes total cost
Data volume or row limits A cheap plan can become expensive once you exceed a cap
Refresh frequency limits Real-time or frequent refresh is often a higher tier
Trial length and what it includes A trial that excludes key features hides the real cost
Overage and add-on fees Connectors, extra storage, and embedding are common add-ons

Get the current numbers from slemma.com/plans-pricing and from each competitor's pricing page, then build a simple total-cost estimate for your actual number of users and data volume.

Collaboration and skill level

This decides whether the tool gets adopted or abandoned.

  • Who builds dashboards: analysts only, or business users too? A drag-and-drop tool lowers the barrier; a SQL-first tool raises it.
  • Sharing and permissions: can you control who sees which dashboard, and can you share with people who have no account?
  • Collaboration features: comments, scheduled email reports, version history.
  • Onboarding cost: how long until a non-technical teammate produces their first useful dashboard?

A useful test: give one non-analyst on your team a 30-minute task in the trial. If they can produce a shareable chart, the tool fits a self-service culture. If not, budget for an analyst to own it.

How to run the comparison

  1. Write down your top three reporting questions and your data sources.
  2. Start trials for Slemma and two or three alternatives at the same time.
  3. Build the same dashboard in each, using the same data.
  4. Record time-to-first-dashboard, missing connectors, and any feature behind a higher tier.
  5. Price each option for your real user count and data volume.
  6. Choose based on the dimension that is a hard constraint for you — usually connectors or per-seat cost — and treat the rest as tiebreakers.

The short answer: Slemma is worth including if its connectors match your stack and its trial lets you test the features you need. Verify pricing and trial terms on its pricing page, and let data connections and total cost per user decide the rest.

What Is Slemma?

Slemma is a business intelligence (BI) and analytics platform for building dashboards and visual reports from connected data sources. Based on the site's own title and description, it positions itself as "Business Intelligence by Slemma | Analytics and Dashboard Software." If you need a tool to pull data together and present it as dashboards rather than to run heavy statistical modeling, that is the category it belongs to.

What Slemma Is Used For

The core purpose implied by its positioning is straightforward: connect data, then turn it into dashboards and visual analysis that a team can read and act on.

Typical jobs it fits:

  • Consolidating data from more than one source into a single view
  • Building dashboards that update as the underlying data changes
  • Producing charts and visual reports for stakeholders who won't query data themselves
  • Giving teams a shared place to look at metrics instead of scattered spreadsheets

Who It's For

Slemma targets teams and businesses that need data insight but aren't necessarily staffed with dedicated data engineers. The emphasis on dashboards and analytics software suggests the intended user is someone who wants to assemble and share reporting, not someone building a data pipeline from scratch.

If your situation looks like one of these, it's worth evaluating:

  • A small or mid-sized team with metrics spread across several tools
  • A business function (marketing, ops, finance) that needs recurring reports
  • An organization that wants a dashboard layer on top of existing data

How It Differs From General Analytics Tools

The distinction that can be confirmed from the site is scope: Slemma is framed as BI and dashboard software, not as a general-purpose analytics or statistics package. In practice that means the value is in connecting sources and presenting results visually, rather than in advanced modeling.

A useful way to decide: if your main problem is "we have data in several places and no shared view of it," a dashboard-oriented BI tool is the right shape. If your main problem is "we need to run experiments and statistical tests," you're looking at a different category of tool.

Pricing and Trying It

The site references a free trial and has a dedicated pricing page at https://slemma.com/plans-pricing. Specific plan tiers, costs, and any login requirements aren't confirmed in the available material, so check that page directly before assuming what a trial includes or what a paid plan costs.

Practical Next Step

To judge whether Slemma fits, do this:

  1. Open the pricing page and confirm the trial terms and plan limits.
  2. List the data sources you'd actually need to connect.
  3. Check whether those sources are supported before investing time in setup.
  4. Build one real dashboard from your own data during the trial — that tells you more than any feature list.

The main thing to verify early is data source coverage, since a BI tool's usefulness depends almost entirely on whether it can reach the data you already have.

Where to Find Slemma Pricing and Product Information

Slemma's pricing information is published at https://slemma.com/plans-pricing, and the main product entry point is its homepage at slemma.com. The site is a JavaScript-rendered app, so if you open it and see only a blank page or a "You need to enable JavaScript to run this app" message, that is expected behavior rather than a broken link — enable JavaScript in your browser and reload.

Direct links to start from

What you need Where to go
Pricing and plan comparison https://slemma.com/plans-pricing
Product overview and main navigation https://slemma.com
Free trial / getting started Linked from the pricing page and site navigation

The site's own navigation references "Pricing" as a top-level link, which is the most reliable path if the URL above ever changes.

What the public pages do and do not tell you

The available site material confirms that Slemma is positioned as Business Intelligence and dashboard/analytics software, and that a free trial and a pricing page exist as entry points. It does not publish, in the material available here, specific plan tiers, per-user costs, billing periods, or payment methods. Treat any specific number you see quoted elsewhere as unverified until you read it on the pricing page itself.

Because of that, the practical approach is:

  1. Open the pricing page and note the plan names and what each one includes.
  2. Check whether the free trial requires a credit card before you start — this is stated (or not) at signup, not in advance.
  3. If your decision depends on seat count, data source limits, or refresh frequency, confirm those on the pricing page rather than assuming they scale with plan level.

Getting help or contacting the vendor

Support and contact routes are reached through the site's own navigation rather than a fixed public URL. If you cannot find a contact link, the pricing page is usually the fastest place to look, since vendors typically place sales contact options next to plan details.

A note on the JavaScript requirement

If you are checking Slemma from a script, a scraper, or a browser with JavaScript disabled, you will get the app shell instead of content. Use a normal browser session with JavaScript enabled, or a headless browser that executes scripts, if you need to read the pricing details programmatically.

How Slemma Pricing Works and How to Choose a Plan

Slemma's pricing is organized around a plans-and-pricing page at slemma.com/plans-pricing, and the site also signals a free trial as an entry point. Because the public page requires JavaScript to render and the captured page evidence contains no plan names, tier limits, or dollar figures, the only reliable way to get current numbers is to open that page directly or contact Slemma. What follows is how to read the pricing structure and decide which tier fits, without inventing figures the source doesn't provide.

What the pricing page actually tells you

The site exposes two pricing-related signals:

  • A Pricing link pointing to https://slemma.com/plans-pricing
  • A free trial reference in the site's pricing keywords

That's the extent of what's verifiable from the source. No plan names, seat counts, data-source limits, or prices are published in the captured content, so treat any specific number you see elsewhere as unconfirmed until you check the page yourself.

How to read a BI pricing page like this one

Business intelligence tools typically differentiate plans along a few axes. When you open Slemma's pricing page, map each tier against these dimensions:

Dimension What to check Why it matters
Users / seats Per-user vs. flat rate, viewer vs. editor roles Dashboards are usually shared; viewer seats are often cheaper
Data sources Number and type of connectors allowed Determines whether you can centralize all your sources
Refresh frequency Manual, scheduled, or real-time Affects how current your reporting is
Dashboard / report limits Cap on dashboards or storage A hidden ceiling on growth
Support and SSO Included or add-on Matters once you roll out beyond a pilot

Which plan fits which situation

Without published tier details, choose by matching your situation to the questions above:

  • Evaluating the tool — start with the free trial to test connectors against your real data before committing.
  • Small team, few sources — an entry tier is usually enough if you only need a handful of dashboards and manual or daily refreshes.
  • Multiple data sources or many viewers — look for a tier that doesn't cap connectors or viewer seats, since these are the most common upgrade triggers.
  • Enterprise rollout — check for SSO, role-based access, and support terms, which are typically gated to higher tiers.

Getting the exact price and starting a trial

  1. Open https://slemma.com/plans-pricing in a browser with JavaScript enabled — the app won't render otherwise.
  2. Compare each tier against the table above using your own user count and data-source list.
  3. Look for the free-trial signup, which the site references, to test before paying.
  4. If pricing isn't shown publicly, use the site's contact option to request a quote.

The key caveat: because the source doesn't publish plan names or prices, confirm every figure on the live page or with Slemma directly before budgeting.

Does Slemma Offer a Free Trial, and How Can I Get Started?

Slemma's site lists a free trial among its pricing signals, and it has a dedicated pricing page at slemma.com/plans-pricing where trial and plan details live. Beyond that, the public page evidence is thin — the site's rendered content is a JavaScript app shell ("You need to enable JavaScript to run this app."), so exact trial length, feature limits, and credit-card requirements aren't visible in the source material. Treat the steps below as the general onboarding path for a BI tool like Slemma, and confirm specifics on the pricing page before you commit.

What the source does and doesn't tell you

Question What's supported What you'll need to check
Is there a free trial? Yes — "free trial" appears as a pricing signal on the site Length, feature scope, and whether a card is required
Where are plan details? slemma.com/plans-pricing Current tiers, seat limits, and billing terms
What does the product do? Business intelligence, analytics, and dashboard software Connector list, refresh limits, sharing rules

Because the page content is JavaScript-rendered, a plain fetch or text scrape returns almost nothing. Open the pricing page in a normal browser to see the actual terms.

Getting started: the general path

  1. Create an account. Go to slemma.com and start the trial from the signup or pricing page. Expect to provide a work email and, possibly, company details. If a card is requested, note the date the trial converts to paid.
  2. Connect a data source. BI tools of this type typically pull from spreadsheets, SQL databases, and SaaS apps (CRM, ads, analytics). Before signing up, list the systems you actually need and check them against the connector list — a missing connector is the most common reason a trial goes unused.
  3. Prepare your data. Have credentials or API keys ready, and know which tables or sheets you want. Clean, single-header tables import far more smoothly than merged-cell reports.
  4. Build a first dashboard. Start with one question you already know the answer to — e.g., monthly revenue by region — and verify the numbers match your source system. This validates the connection before you invest time in layout.
  5. Test the collaboration features. Sharing, permissions, and scheduled exports are usually where free tiers differ most from paid plans. Try them during the trial, not after.

Deciding whether to continue

Use the trial to answer three questions: does it connect to all your sources, can the people who need the dashboards actually view them under the trial's sharing rules, and does the refresh cadence match how often your data changes? If any answer is no, the paid plan won't fix it.

If your data lives mainly in spreadsheets and you need simple charts, a lighter tool may be enough. If you're consolidating several databases and SaaS sources into shared dashboards, a BI platform is the better fit — but verify connector coverage first.

Common snags

  • JavaScript-only pages. If the pricing page appears blank, disable script blockers or try another browser.
  • Trial-to-paid conversion. Trials often auto-convert; set a calendar reminder before the end date.
  • Connector gaps. Check the specific integration you need rather than assuming "it connects to everything."
  • Data volume limits. Row or refresh caps on trials can make a test look slower than production will be.

For current trial terms and plan pricing, go directly to slemma.com/plans-pricing — that page is the authoritative source, and the details there may have changed since this was written.

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 2015, this domain has about 11 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 GoDaddy.com, LLC, a widely used domain service provider. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by GoDaddy, indicating managed DNS hosting. MX records point to the Google Workspace email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. 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 is valid for about 198 days in total, with 35 days remaining. The SAN includes a wildcard covering multiple hostnames at the same subdomain level. Shared private keys can increase the impact of a compromise.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. 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 Google Analytics, 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. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 6 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSGoDaddy
HostingAmazon.com, Inc.
EmailGoogle Workspace
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagAshburn, Virginia, United States Inferred 35.169.208.136

Registration details

RDAP / WHOIS

RegistrarGoDaddy.com, LLC
Registered2015-04-08
Expires2027-04-08
Domain statusclient delete prohibited、client renew prohibited、client transfer prohibited、client update prohibited
Nameserversns13.domaincontrol.com、ns14.domaincontrol.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aslemma.com35.169.208.136321—
MXslemma.comaspmx.l.google.com36001
MXslemma.comalt1.aspmx.l.google.com36005
MXslemma.comalt2.aspmx.l.google.com36005
MXslemma.comaspmx2.googlemail.com360010
MXslemma.comaspmx3.googlemail.com360010
MXslemma.commxa.mailgun.org360010
MXslemma.commxb.mailgun.org360010
NSslemma.comns13.domaincontrol.com3600—
NSslemma.comns14.domaincontrol.com3600—
TXTslemma.com3k0fggfv48ly3gqzb3y1jkxhh2ksm3yd3600—
TXTslemma.com4jmIRa9frOkB5xj0WvaAIJ2LpSJkCp6zuDyG_mdSLto3600—
TXTslemma.comgoogle-site-verification=5WYcC9zWxP6LTGorC5Ixe12NZ2wU2iqfSEfEG97driw3600—
TXTslemma.comgoogle-site-verification=5rGayFz_Xh6JDjgIBFx64nXqlaZqNKgzSLjTlXsWr7Q3600—
TXTslemma.comgoogle-site-verification=6Jr9EgKy4xRkPILowf4LYBKzxqh_NDixRh22DsW0tJM3600—
TXTslemma.comgoogle-site-verification=F-hr6r4LX3y8phPxAfp-gbN1ICbe13NAcQrY-i4iePI3600—
TXTslemma.comgoogle-site-verification=hctq-FMxTvLrMdxyOZaC8p4g9QaKwgOj_8JBqt7tgqo3600—
TXTslemma.comgoogle-site-verification=i2kKrM6CjumE8E9pMuPTP9SpDk3lZrl3YabaojyzrkA3600—
TXTslemma.comhubspot-developer-verification=Y2U4OTZkMzAtYTc0Mi00M2I5LThhY2QtYjQ5YzA5ZjhlM2Fi3600—
TXTslemma.comv=spf1 include:_spf.google.com include:spf.mail.intercom.io ~all include:mailgun.org ~all include:infusionmail.com ~all3600—
DMARC_dmarc.slemma.comv=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2
Negotiated protocolTLSv1.2
Certificate subject*.slemma.com
IssuerGoDaddy.com, Inc.
Valid until2026-11-11T14:03 · Remaining when checked: 35 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html
servernginx
strict-transport-securitymax-age=63072000

Identified technologies

Google Analyticsnginx

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

No robots.txt found

No sitemaps found

User reviews (0)

  • No reviews yet.