AWS costs: How to read Cost Explorer - a 15-minute literacy course

Reading AWS Cost Explorer comes down to four moves: pick the right cost number (usually amortized, not the unblended figure it shows you by default), group by Service or Linked Account first, filter down to one cost driver at a time, then switch the time range to see whether you're looking at a trend or a one-off spike. That's the whole skill — everything else is just knowing which button does what. Here's the part almost nobody explains: the big number sitting front and center, unblended cost, is a cash-basis figure by design, and it quietly hides your true per-resource cost the moment you buy a Savings Plan or a Reserved Instance.

Jake found Cost Explorer the way most small business owners do: by accident, while trying to figure out why his AWS bill for the shop's repair-ticket app and inventory backups jumped by $140 in one month. "I clicked into this cost thing," he told Ethan, "and there's a graph, some colored bars, a percentage that says 'forecasted,' and a button that says 'Analyze with Amazon Q.' I don't know which of these numbers is the one I'm supposed to worry about."

That's a fair question, and it's the right first question. Cost Explorer isn't complicated because the data is hard to get — AWS hands it to you for free the moment you open the console. It's complicated because it shows you six or seven different ways of describing the same spend, and the tool never tells you which one you actually want. This is the 15-minute version: what each part of the screen means, which number to trust, and how to point the two main controls — Group by and Filter — at any question you have about your bill.

What Cost Explorer Actually Shows You

AWS Cost Explorer is a free interactive tool inside the Billing and Cost Management console that queries the same underlying dataset used to build your AWS invoice and your detailed Cost and Usage Reports. It draws that data as a graph and a table, and it lets you slice it by service, account, region, tag, and a dozen other dimensions without writing a single line of code.

It is not a separate billing system, and it is not an estimate pulled from a different source than your bill. It's a window into the same records that generate your invoice — which is exactly why the numbers can look strange the first time you open it. You're not looking at a summary someone wrote for you; you're looking at raw cost records, filtered however you tell it to filter them.

The console interface itself costs nothing to use, no matter how many times you load it or how many reports you build. The only two ways Cost Explorer charges you anything are the programmatic API (covered later) and optional hourly-granularity data. Everything you'll do in your first fifteen minutes — opening the dashboard, changing the date range, grouping by service — is free.

Cost Explorer also ships five preconfigured reports you can open without building anything yourself: monthly cost by service, monthly cost by linked account, monthly EC2 running hours cost and usage, daily costs, and AWS Marketplace costs. If you want to move from the dashboard into the full report builder — the screen where Group by and Filter actually live — choose Explore costs in the upper-right corner of the dashboard.

Getting Access: Enabling Cost Explorer and the Permissions You Need

If you've never opened Cost Explorer on this account, the console walks you through a one-time enablement step before it shows you anything. You can't turn Cost Explorer on through the API — it has to happen in the console — and once it's on, you can't turn it back off.

Enabling Cost Explorer for the first time

1. Sign in to the AWS Management Console and open the Billing and Cost Management console at console.aws.amazon.com/costmanagement.
2. In the navigation pane, choose Cost Explorer. On a brand-new account, you'll be prompted to enable it.
3. Wait roughly 24 hours for the current month's data to appear. The rest of your historical data — back to your account's start, or the last 13 months, whichever is shorter — takes a few days longer to fully populate.
4. Come back after that window and you'll land on the Cost dashboard, which is the default view described below.

Once it's populated, Cost Explorer refreshes your cost data at least once every 24 hours, so a fix you made yesterday (deleting an idle resource, say) won't visibly move the graph until the next refresh.

On the permissions side: if you're the account owner, you already have access. If someone else on your team needs to view Cost Explorer without being able to change billing settings, they need an IAM policy that grants the relevant ce:* actions — for example, ce:GetCostAndUsage for the standard view, or ce:GetCostAndUsageComparisons and ce:GetCostComparisonDrivers specifically for the Compare feature covered later in this post. If you're inside an AWS Organizations setup, only the management account can enable Cost Explorer for the organization; after that, member accounts can see it too, scoped to what their account is allowed to view.

The Cost Dashboard: Five Numbers, Decoded

When you first open Cost Explorer, you land on the Cost dashboard, not the interactive report builder. It's a fixed summary made of a handful of pieces, and knowing what each one is telling you saves you from misreading the whole page.

Your estimated costs for the month to date. This is a running total for the current calendar month only, calculated from the data that's landed so far. It is not your final bill, because AWS billing data continues to settle for a few days after the month closes — treat it as "close, and getting closer as the month goes on," not as a locked number.

Your forecasted costs for the month. A projection of where your spend is likely to land by month's end, based on your usage pattern so far this month layered onto your recent history. The Forecast section further down covers exactly how much to trust this number.

A graph of your daily costs. The main visual — daily spend as bars or a line, for the current month by default. This is the piece people stare at and misread most, because a single tall bar can mean a real problem or a scheduled batch job that runs once a week. The granularity section further down covers that trap.

Your top cost trends. A short list highlighting the services or accounts with the biggest month-over-month change, so you don't have to hunt for what moved. This is a lightweight preview of the fuller Cost Comparison feature covered further down.

Recently viewed reports, and an "Analyze with Amazon Q" button. The dashboard also lists reports you've recently built, and offers an AI-generated explanation of any report you're looking at, plus an "Ask question" box for typing a cost question in plain language. Both are optional — everything they can tell you, you can also find yourself using the techniques in this post, which is worth knowing if your organization restricts access to Amazon Q features.

Unblended, Amortized, Blended, and Net: Picking the Right Cost Number

This is the setting that quietly changes every other number on the page, and it's the one almost no beginner touches, because it's tucked into a dropdown rather than presented as a decision. Cost Explorer can show you the same period of spend as five different metrics, and they are not close-enough-to-interchangeable — for anyone using Reserved Instances or Savings Plans, two of them can tell noticeably different stories about the same month.

Unblended cost — the default, cash-basis view

Unblended cost reflects what you were actually charged on the day a charge posted, with no smoothing and no distribution over time. If you think of accounting in cash-basis terms — an expense counts on the day you paid it — unblended cost is that. It's the default metric because it's the most literal, and for anyone without Reserved Instances or Savings Plans, it's also the simplest to read correctly: the daily number is the daily charge.

Amortized cost — the accrual view, and the honest one

Amortized cost spreads recurring or upfront commitment fees — an EC2 Reserved Instance, a Savings Plan — evenly across the period they cover, instead of dumping the whole charge on the day you paid it. If you pay $1,200 upfront for a one-year Savings Plan, unblended cost shows $1,200 on day one and nothing for the rest of the year; amortized cost shows roughly $100 a month for twelve months. That second view is the one that actually tells you what a given day, week, or resource cost you in reality.

Blended, net unblended, and net amortized

Blended cost averages rates across every linked account in a consolidated-billing family, which made more sense before Savings Plans existed and is rarely the right default today. Net unblended and net amortized are the same two calculations as above, adjusted to include Amazon-applied discounts and credits, which matters if your organization negotiates enterprise discounting and wants to see the after-discount reality.

One extra layer worth knowing: Cost Explorer applies discounts to your forecast by default, and on the unblended monthly view you can see exactly how much of a given month's bill was reduced by commitment discounts — it appears in the graph as RI Volume Discount. If you want the same figure as it appears on your actual invoice, open Bills in the navigation pane and expand Total Discounts under Credits, Total Discounts and Tax Invoices — the two numbers are designed to match.

Ethan doesn't hedge on this one. "Unblended is the metric AWS shows you because it's the simplest to compute, not because it's the most useful," he says. "The moment you buy a commitment of any kind, unblended cost starts lying to you about individual days by design — not maliciously, just structurally. Amortized is the only one of the five that tells the truth about a Tuesday."

Jake wasn't convinced at first. "But the bill I actually pay is the unblended number, right? Isn't that the 'real' one?" Ethan's answer: "It's real in the sense that it's what left your bank account that day. It's not real in the sense of telling you what that Tuesday's usage actually cost. Those are two different questions, and Cost Explorer answers both — you just have to pick which one you're asking."

Group By and Filter: The Two Levers That Answer Any Question

Every real question you'll ever ask Cost Explorer — "what's driving this," "whose spend is this," "did this region cost more than that one" — gets answered with the same two controls, used together. Filter narrows the dataset down to what you care about. Group by splits that narrowed dataset into named buckets so you can see which bucket is heaviest.

The standard first move, before you filter anything, is to disable every filter and group by Service. That gives you an unbiased top-down view: which services are actually costing you money this month, largest first. Once you spot the outlier — say, Amazon S3 is higher than you expected — you filter to just that service and group by a second dimension, like Usage Type, to see the components underneath it.

You can group by up to two dimensions at once — either standard dimensions, tag keys, or Cost Categories, in any combination — which is enough to answer almost any drill-down question in two clicks instead of ten.

Filters work the same way in reverse — you can filter by any of these dimensions, plus a handful more like instance type, operating system, and API operation, and you can combine several filters at once. The practical workflow is almost always: group broad, filter narrow, then swap the second group-by dimension until the number in front of you actually explains itself.

Reading the Graph: Granularity, Time Range, and the Averaging Trap

Cost Explorer's graph can show Daily, Monthly, or Hourly granularity, and switching between them changes what a spike actually means. A single tall bar on a Daily view might be a real problem — or it might be a weekly batch job, a monthly snapshot, or an annual Reserved Instance renewal that only happens once. Switch to Monthly and that same spike often disappears into the average, which is exactly why relying on the monthly number alone can hide a real, recurring weekly cost until it's added up to something large.

By default you can view up to the last 13 months of history at daily or monthly granularity. If you turn on multi-year data at monthly granularity, that window extends to as much as 38 months back — useful for spotting a slow, year-over-year creep that a 13-month window would never show you. Hourly granularity is narrower in the other direction: it only covers the last 14 days, and only for two things — overall cost and usage without resource-level detail, and EC2 resource-level detail specifically. Hourly data is also the one part of the free console that isn't free (more on that below).

Resource-level detail isn't limited to EC2, though EC2 is the only service with resource-level detail at hourly granularity. Separately, you can turn on resource-level data at daily granularity for any service you've actually used in the last six months — AWS ranks the eligible services by cost in a dropdown when you set it up — and once enabled, Group by: Resource shows you cost per specific resource ID for the past 14 days. Anything you haven't enabled resource-level data for still shows up in Cost Explorer, just bucketed under "No resource ID" instead of broken out individually — which is a fast way to check whether that granularity is even worth turning on for a given account.

The averaging trap works both ways. A cost that looks alarming on a Daily view can be entirely normal once you see it's a predictable weekly pattern. And a cost that looks fine on a Monthly view can be quietly ballooning week over week in a way the monthly total is still too small to flag. The fix is the same either way: before you decide a number means anything, look at it in at least two granularities.

Tags and Cost Categories: Making Cost Explorer Answer "Whose Spend Is This"

Grouping by Service tells you what costs money. Tags tell you who or why. If Jake ran three AWS resources — one for the shop's website, one for inventory, one for a side project he's testing — cost allocation tags are how he'd split the bill between them instead of staring at one combined total.

There are two kinds of cost allocation tags. AWS-generated tags carry an aws: prefix and are created automatically — createdBy is one example, tracking who created a resource. User-defined tags carry a user: prefix and are the ones you create and apply yourself, like project or team. Both kinds have to be separately activated before Cost Explorer will let you group or filter by them — applying a tag to a resource is not the same step as activating it for billing.

Activating a user-defined cost allocation tag

1. Sign in to the AWS Management Console and open the Billing and Cost Management console at console.aws.amazon.com/costmanagement.
2. In the navigation pane, choose Cost allocation tags.
3. Select the tag key or keys you want to activate.
4. Choose Activate.

Only the management account of an Organization, or a standalone account that isn't part of one, has access to this tag manager — a member account can't activate its own tags. Note that this is only available to the management account or a standalone account.

Cost Categories are a related but different tool. Where a tag is a label you attach to individual resources, a Cost Category is a rule-based grouping you define at the account level — for example, mapping several linked accounts, services, or tag values into one named bucket like "Production" or "Client A," without having to tag every resource by hand. You can group and filter by Cost Categories the same way you group by a tag or a standard dimension, which makes them the better tool once tagging every single resource stops being practical.

Cost Comparison and Anomaly Detection: Finding What Changed

Manually grouping and filtering to find what changed month over month works, but AWS also ships a feature built specifically for that question: Cost Comparison. It automatically identifies the largest cost changes between two selected months — across services, accounts, and Regions — and breaks the change down into causes: usage changes, discount changes, and other charge types like fees or credits.

Using Cost Comparison

1. Open the Billing and Cost Management console and choose Cost Explorer in the navigation pane.
2. In the Report parameters panel, choose Compare.
3. Pick Relative to compare this month against last month, or Absolute to pick any two specific months within your available history.
4. Review the driver breakdown for each significant change — the graph and table update in real time as you narrow by service, account, tag, or other dimensions.

There's also a Top Trends widget on the Billing and Cost Management console home page, which surfaces the ten biggest cost variations between the previous two months without you having to build a report at all — a faster way to catch a surprise before it becomes a pattern.

Cost Comparison tells you what already changed. If you want to be alerted the moment an unusual spend pattern starts, that's a separate but related feature: Cost Anomaly Detection. It uses machine learning to evaluate your normal weekly and monthly spending patterns and flags deviations, sending alerts by email or through an Amazon SNS topic — which you can route into Slack or Amazon Chime. Detected anomalies also show up directly in the Cost Explorer console, with AWS's best estimate of the largest contributing cause. It's a separate service you set up on top of Cost Explorer, not a toggle inside the reports you've already built, so it's worth setting up once rather than expecting the dashboard to catch everything on its own.

The Forecast Tab: What It Can and Cannot Tell You

Cost Explorer's forecast is built from your historical and current cost patterns, and it's available at no extra charge alongside the console you're already using. Ask it for a daily forecast and you can look up to 3 months ahead; ask for a monthly forecast and you can look further out.

Under the hood, the forecast always returns a single mean value — its single best guess — but you can also ask for a prediction interval by setting a confidence level between 51 and 99. A higher confidence level widens the range Cost Explorer is willing to commit to, which is a useful reminder that the forecast is a statistical range, not a promise. AWS also offers AI-generated explanations, currently in preview, that describe how a given forecast was calculated, if you want the reasoning rather than just the number.

Reservation and Savings Plans Recommendations, in Plain English

Once you've read your costs correctly, the natural next question is whether you could pay less for the same usage. Cost Explorer's Savings Plans recommendations tackle exactly that: based on a lookback period you choose — 7, 30, or 60 days of past On-Demand usage — it suggests a commitment level, term, and payment option designed to cover as much of your steady, predictable usage as possible at a discount.

The lookback period matters more than it sounds like it should. A 7-day lookback reacts quickly to a recent change in usage but can be thrown off by an unusually busy or quiet week; a 60-day lookback smooths that out but reacts more slowly if your usage pattern has genuinely shifted. If your workload is new or still changing shape, start with the shorter window and revisit it once your usage settles.

Recommendations are just that — recommendations. Nothing purchases automatically. You review the suggested commitment, its estimated coverage and utilization impact, and only then choose to add it to your Savings Plans cart. This is a genuinely useful feature once your usage is stable, and one you should ignore entirely if you're still in an experimental or highly variable phase — committing to a year of spend on a pattern that's about to change is how "saving money" turns into wasted money.

What Cost Explorer Can't (and Won't) Tell You

Knowing the edges of the tool matters as much as knowing its controls, and this is the part most quick guides skip over.

It has a data-volume ceiling. Resource-level data at daily granularity, and the two hourly-granularity features, are each capped at 500 million usage records. Push past that and Cost Explorer won't save your preferences — it hands you a data threshold error and points you toward the AWS Cost and Usage Report (CUR) instead, which has no such ceiling and can include resource IDs at hourly granularity for every service, not just EC2.

It can't act on anything it shows you. Cost Explorer will tell you a service is trending upward; it won't shut anything down, cap anything, or reduce anything for you. If you want an automatic threshold alert, that's AWS Budgets, layered on top of the same data. If you want an automated shutdown, that's your own Lambda function or a third-party tool watching the same numbers.

It reads Billing Conductor accounts differently. If your organization uses AWS Billing Conductor to build custom, resold, or re-priced billing groups, granular data — hourly and resource-level — isn't visible in Cost Explorer for accounts inside a standard billing group or a billing transfer group. The high-level Group by and Filter views still work; it's specifically the granular add-ons that don't reach through a Billing Conductor setup.

It won't explain a cost it can't see. Cost Explorer only shows chargeable AWS costs. Spend on a non-AWS cloud provider, or anything that never posted as a standard AWS charge, never appears here no matter how you filter, because it was never in the dataset to begin with.

The Cost Explorer API: When the Console Isn't Enough

Everything covered so far happens in the free console. If you want to pull the same data into your own dashboard, a spreadsheet macro, or an automated Slack report, that's the Cost Explorer API — and it's the one part of this whole tool that has a real, per-use price tag.

Each paginated API request against your primary billing view costs $0.01. If you've combined several billing views into one custom view — say, five source accounts merged into a single view — each request against that combined view costs $0.01 per source, so five sources means $0.05 per request. Hourly granularity data, whether requested through the console or the API, is billed separately at $0.00000033 per usage record per day, which works out to roughly $0.01 per 1,000 usage records a month.

For most individuals and small businesses, the console alone answers every question in this post at zero cost, forever. The API earns its keep only once you're building something that needs the data outside the console — a chargeback report, a custom internal dashboard, or an integration with a tool like a spend-management platform.

Five Ways Cost Explorer Gets Misread

Knowing the controls is half the skill. Knowing where people go wrong with them is the other half — these are the patterns that keep showing up.

1. Trusting the default metric without checking it. Anyone with a Reserved Instance or Savings Plan who never switches from Unblended to Amortized is reading a distorted picture of their own spend, every single time they open the tool. The fix is one dropdown, done once, and then remembered.

2. Reading month-to-date as if it's the final bill. The month-to-date figure grows every day the month is still in progress; it is not a prediction of where the month ends up, and it is not a settled invoice amount even after the month closes, because billing data keeps settling for a few days afterward.

3. Grouping by a tag before activating it. The tag exists on the resource. Cost Explorer still can't see it until it's been activated and the data has caught up — which, as covered above, can take up to 48 hours combined.

4. Judging a spike on a single granularity. A daily spike that looks alarming can be a routine weekly pattern; a monthly total that looks stable can be hiding a weekly climb. Check both before you act.

5. Assuming forecast confidence means certainty. The forecast is a statistical projection with a mean value and an optional prediction interval — not a locked number. It gets more reliable as the month progresses and more history accumulates, and it's least reliable in the first few days of a new billing period.

Organizations, Member Accounts, and Multi-Year Data

If your AWS setup involves more than one account under AWS Organizations, a few things behave differently than they do for a single standalone account. Cost Explorer has to be enabled at the management account level before member accounts can use it at all. A management account can view cost and usage data across every member account it manages; a member account, by contrast, can typically only see its own spend, not its siblings' — which is by design, and useful if different accounts belong to different teams or clients who shouldn't see each other's numbers.

Cost allocation tags follow the same management-account-only rule: only the management account (or a standalone account not in an Organization) can activate tag keys. And if an account ever moves from one Organization to another, its previously activated tags lose their active status in the new Organization and need to be reactivated by the new management account — a detail that's easy to miss and shows up as "my tags stopped working" after a restructuring.

On history: the standard window is up to 13 months of data at daily or monthly granularity, which covers almost every practical question. If you need to see a slower, multi-year trend — how your total spend has grown year over year, say — you can enable multi-year data at monthly granularity to extend that window out to as much as 38 months. It's a setting worth turning on once and leaving on, rather than something to enable reactively after you've already wanted the older data and found it wasn't there.

Frequently Asked Questions

Is AWS Cost Explorer free to use?

Yes, the console itself is free — viewing the dashboard, building reports, switching cost metrics, grouping and filtering, all at no charge. The only costs attached to Cost Explorer are the API, at $0.01 per paginated request, and optional hourly-granularity data, at roughly $0.01 per 1,000 usage records a month.

What's the real difference between unblended and amortized cost?

Unblended cost shows what you were charged on the day a charge posted — a cash-basis view. Amortized cost spreads commitment fees like Reserved Instances and Savings Plans evenly across the period they cover, so a $1,200 upfront payment shows as roughly $100 a month for a year instead of $1,200 on day one. If you own any commitment discount, amortized is the number that reflects your actual daily cost.

Why don't the numbers in Cost Explorer match my invoice exactly?

Two common reasons. First, if you're viewing a metric other than the one used to generate your invoice — for example, amortized instead of unblended — the totals will legitimately differ, since they're describing the spend differently, not incorrectly. Second, billing data continues to settle for a few days after the month closes, so a number checked mid-month or right at month-end may not yet match a finalized invoice.

How far back does Cost Explorer's data go?

Up to 13 months by default, at daily or monthly granularity. If you enable multi-year data at monthly granularity, that extends to as much as 38 months of history.

Can I see hourly-level cost data?

Yes, but only for the last 14 days, and only after enabling it. Hourly granularity covers overall cost and usage without resource-level detail, plus a separate EC2 resource-level view, and it's billed at roughly $0.01 per 1,000 usage records a month rather than being free.

Why can't I group my costs by a tag I just created?

Tags have to be activated separately from being applied to a resource, and there's a delay built into the process — up to 24 hours for a new tag key to appear on the activation page, and up to another 24 hours after activation before it starts populating in Cost Explorer. It isn't broken; it just hasn't caught up yet.

What's the difference between a cost allocation tag and a Cost Category?

A tag is a label you attach to an individual resource. A Cost Category is a rule-based grouping you define once at the account level, mapping accounts, services, or tag values into named buckets like "Production" or a client name, without tagging every resource by hand. Both can be used to group or filter in Cost Explorer.

How do I quickly find out why my bill jumped this month?

Use the Cost Comparison feature: open Cost Explorer, choose Compare in the Report parameters panel, and select the two months you want to compare. It automatically surfaces the biggest drivers of change and breaks them down into usage changes, discount changes, and other charges like fees or credits, so you don't have to hunt for it manually.

Will Cost Explorer show costs from before I started tagging resources?

No. Tags apply only from the point a resource carries them onward; a resource created before the tag existed won't retroactively show that tag on its historical spend. If clean cost allocation matters to you, apply your tags before you launch the resource, not after.

When do I actually need the Cost Explorer API instead of the console?

Only when you need cost data outside the console itself — feeding a custom dashboard, an automated report, or a script. Every technique in this post works free, inside the console, with no API involved. The API costs $0.01 per paginated request, so it's worth reaching for only once the console genuinely can't do what you need.

How soon after opening a new AWS account does Cost Explorer show data?

The current month's data is usually available about 24 hours after you enable Cost Explorer. The rest of your historical data takes a few days longer to fully populate.

Can a member account in an AWS Organization see the whole organization's spending?

Generally, no. The management account can see cost and usage data across every member account it manages, but a member account typically only sees its own spend. Cost Explorer also has to be enabled at the management-account level before any member account can use it.

What's the difference between Cost Explorer and AWS Budgets?

Cost Explorer is for exploring and understanding costs you've already incurred, or forecasting where they're headed — it's an analysis tool. AWS Budgets is for setting spending thresholds and getting alerted when actual or forecasted spend crosses them — it's an enforcement and alerting tool. They read from the same underlying billing data and work well used together: Cost Explorer to understand a pattern, Budgets to be warned before it repeats.

How accurate is the Cost Explorer forecast, and can I trust it for budgeting?

It's a statistical projection based on your historical and current usage, not a guarantee. Cost Explorer always gives you a single mean value, and you can additionally request a prediction interval by choosing a confidence level between 51 and 99 — the higher the confidence level, the wider the range it commits to. Treat it as a planning range that gets more reliable as the month progresses, not as a locked number early on.

Why is there a cost for a service I don't remember using?

Group by Service, find the unfamiliar line, filter down to just that service, and then group by Usage Type to see the specific billed component driving it. Many surprise charges turn out to be a supporting service triggered automatically by something you did intentionally elsewhere — a snapshot, a data transfer, a logging service — rather than an unrelated or mistaken charge.

Can I export Cost Explorer data to a spreadsheet?

Yes. Any report you build in Cost Explorer can be downloaded as a CSV file of the exact data behind your graphs and tables, and you can also save the report's configuration — filters, groupings, and date range — as a bookmark or a saved report so you don't have to rebuild it next time.

Revision note. Written September 2026, covering the current Cost Explorer console, its cost metrics, Group by and Filter dimensions, tag activation rules, Cost Comparison, Cost Anomaly Detection, forecasting, Savings Plans recommendations, granular-data limits, and API pricing as documented by AWS at the time of writing. AWS periodically renames console panels and adjusts forecast horizons and lookback windows, so a specific number here may shift before this note does. If your bill still doesn't make sense after working through this, that frustration is completely fair — the tool buries its best feature, the metric dropdown, behind the least obvious label on the page, and you deserve better than to find that out the hard way.Happy learning, See you on next post..!