Statuses and what they mean
This page lists every status the HostRepute portal shows, one table per area, so you can look up a scan status meaning or any other label you see next to a domain, IP, check or alert.
- A failed scan or a blocklist that didn’t answer is a warning, not a listing. Only a blocklist that lists the domain or IP makes it Listed. Blocklist monitoring explains why.
- The portal shows the words in the Status column. The API, the MCP server and webhook payloads carry the matching internal values, which can be worded differently.
Domain and IP scan status
Section titled “Domain and IP scan status”| Status | Meaning |
|---|---|
| Not scanned yet | No blocklist scan has run for it yet. A monitored domain or IP gets its first scan shortly after you add it; a paused one isn't scanned. |
| Checking | A scan is running; its page says Scanning now until it finishes. A domain or IP that is already listed keeps showing Listed while it's rescanned. |
| Clean | The latest scan finished and none of the blocklists in its check profile lists it. It only shows after a completed scan, never before the first one. The dashboard's recent list shows it as No listings. |
| Listed | At least one blocklist in its check profile lists it. It stays listed until a later scan comes back clean from the blocklists that listed it, so a failed or partial rescan doesn't clear it. The On a blocklist filter shows these. |
| Scan failed | The latest scan didn't finish because no blocklist answered, usually for a moment. This is a warning, not a listing: it says nothing about reputation, and HostRepute tries again on the next scheduled check. |
| Paused | Monitoring is turned off for it, so it isn't scanned and keeps its last result next to this badge. The dashboard shows it as Monitoring off unless it's listed. |
Scan result
Section titled “Scan result”| Status | Meaning |
|---|---|
| Clean | The scan finished and no blocklist that answered listed it. Blocklists that didn't answer are marked as such in the scan's details. |
| Listed | At least one blocklist that answered listed it in this scan. |
| Checking | The scan is still running; results fill in as each blocklist answers. |
| Scan failed | No blocklist answered, or none ran, so the scan has no result. It doesn't change the listing state or add a point to the score trend, and the credits for a manual scan are refunded. |
Blocklist result in a scan
Section titled “Blocklist result in a scan”| Status | Meaning |
|---|---|
| Listed | This blocklist answered and lists the domain or IP. The row shows how to ask for removal and the raw response. |
| Clean | This blocklist answered and doesn't list it. |
| Didn’t answer | The lookup failed, for example it timed out. It counts as neither listed nor clean and is left out of the blocklist score; a scan only fails when no blocklist answered. |
Reputation score tier
Section titled “Reputation score tier”| Status | Meaning |
|---|---|
| Pending | There's no completed blocklist scan yet, so there's no number. The score card reads Waiting for results. |
| Listed | At least one blocklist lists it in the latest completed scan. The score is capped at 49 while it's listed; on the dashboard, any listed domain or IP makes the overall tier Listed even when the average is higher. |
| Critical | Below 50 with no listing: other signals, such as email authentication or certificates, pull the score down. |
| Review | 50 to 74 with no listing. |
| Good | 75 to 89 with no listing. |
| Excellent | 90 to 100 with no listing. |
Reputation score letter grade
Section titled “Reputation score letter grade”| Status | Meaning |
|---|---|
| A | A reputation score of 90 to 100. Grades use their own cutoffs, separate from the tiers, after rounding the score down. The public report badge shows the score and grade, for example 92 / A. |
| B | 75 to 89. |
| C | 55 to 74. |
| D | 40 to 54. |
| F | 0 to 39. A domain or IP without a score gets no grade, never an F. |
Reputation score signal status
Section titled “Reputation score signal status”| Status | Meaning |
|---|---|
| Good | The signal looks healthy: no listing for Blocklists, no failing or needs-work checks for Email authentication, and a part score of 90 or more for Certificates, Google Postmaster and Microsoft SNDS. |
| Needs work | Email authentication has checks that need work but none failing, or the certificate, Google Postmaster or Microsoft SNDS part score is 70 to 89. Blocklists never show this. |
| Problem | Blocklists: listed on at least one. Email authentication: at least one failing check. Certificates, Google Postmaster, Microsoft SNDS: part score below 70. |
| Not connected | There's no data for this signal yet, for example no email authentication check, certificate check, Postmaster domain or SNDS data for it. It lowers the confidence, not the score. |
| Waiting for data | Blocklists only: there's no completed scan yet, or the latest scan had no blocklists to check. The score stays empty until there is one. |
Reputation score confidence
Section titled “Reputation score confidence”| Status | Meaning |
|---|---|
| High | Signals with data carry at least 80% of the possible weight, for example blocklists, email authentication and certificates (85 of 95). Weights: blocklists 45, email authentication 25, certificates 15, and Google Postmaster (domains) or Microsoft SNDS (IPs) 10. |
| Medium | 60% to 79% of the weight has data, for example blocklists and email authentication (70 of 95). |
| Low | Some data, but under 60% of the weight, for example blocklists alone (45 of 95). |
| Pending | No signal has data yet. On the dashboard the percentage is the average over all your domains and IPs. |
Signal coverage
Section titled “Signal coverage”| Status | Meaning |
|---|---|
| Connected | Every domain and IP this signal applies to has data for it. Google Postmaster counts only domains, Microsoft SNDS only IPs. |
| Partly connected | Some of them have data for it, not all. |
| Not connected | None of them has data for it yet; the card links to where you connect it. |
Public report badge scale
Section titled “Public report badge scale”| Status | Meaning |
|---|---|
| Excellent | On the badge's own scale: a score of 90 or more with no listing, shown green. The badge uses this scale only for reports saved without a reputation tier; other reports color the badge by their reputation score tier. |
| Good | On the badge's scale: 70 to 89 with no listing, shown blue. |
| Review | On the badge's scale: 50 to 69 with no listing, shown amber. |
| Listed | On the badge's scale: any listing, or a score below 50, shown red. This scale has no separate Critical tier. |
| pending | The report has no score yet, so the badge reads pending in gray. |
Email authentication result
Section titled “Email authentication result”| Status | Meaning |
|---|---|
| Passing | This check found what it looks for. |
| Needs work | This check found something to improve, for example a PTR hostname that looks generic or isn't fully qualified. A run with such a check and no failing one reads Needs work overall; each one takes 8 points off the email authentication part of the reputation score. |
| Failing | This check found a problem, for example no SPF record, more than one SPF record or no MX record. Any failing check makes the whole run Failing; each one takes 18 points off the email authentication part of the reputation score. |
| Not checked | The check doesn't apply to the target, for example a domain-only check on an IP, or it needed a PTR record that isn't there. A run where nothing applied reads Not checked overall. |
| All good | Overall result of a run where at least one check passed and none failed or needed work. |
Delisting request status
Section titled “Delisting request status”| Status | Meaning |
|---|---|
| Preparing | You started a request from a listing and are working through the list's checklist. It can move to Ready to send once every checklist item is done. |
| Ready to send | The checklist is done. Send the request to the list (their removal form, an email, or their instructions), then mark it as sent. |
| Sent | You sent the request and are waiting for the list to review it. HostRepute reminds you on the follow-up date. |
| Waiting on the list | The list replied or is reviewing the request. Mark it as removed once the listing is gone; the next scan confirms it too. Follow-up reminders continue. |
| Removed | You marked the listing as removed. HostRepute alerts you if it's listed again. |
| Listed again | The list listed it again after it was removed: you marked it, or a later blocklist check through the API found the listing again. Find out why, then start a new request from the listing. |
| Rejected | The list turned the request down. Fix the cause they gave, then start a new request. |
| Not pursued | You chose not to pursue this listing; the request is closed. |
Alert activity event
Section titled “Alert activity event”| Status | Meaning |
|---|---|
| Listed on a blocklist | A scheduled scan found a domain or IP on a blocklist after it was clean. Alert activity records only blocklist alerts: this one and Removed from a blocklist. |
| Removed from a blocklist | A scheduled scan found a domain or IP clean again after it was listed. |
Alert delivery status
Section titled “Alert delivery status”| Status | Meaning |
|---|---|
| Sent | The alert went out to its channel: right away when the channel follows no delivery hours or one of them is open, otherwise when its delivery hours opened. |
| Held for delivery hours | Every set of delivery hours the channel follows was closed, so the alert waits and goes out when the first one opens. |
| Not sent yet | The alert has no send time yet. A cleanup job sets it to the next opening of its delivery hours, or deletes it when it's more than 7 days old or its delivery hours were deleted. |
Certificate status
Section titled “Certificate status”| Status | Meaning |
|---|---|
| Not checked yet | No check of this certificate has finished yet. HostRepute checks certificates once an hour, so the first check runs within the hour unless it's paused; Check now runs one right away. |
| Valid | The certificate is trusted, covers the name, isn't revoked, has a strong key and signature, is allowed by your CAA records, and isn't close to expiry. |
| Expiring soon | Otherwise valid, but it expires within the largest warning threshold of its check profile (60 days by default). |
| Expired | The expiry date has passed. |
| Not trusted | Still in date, but it fails a trust check: the chain isn't trusted, the name doesn't match, it's revoked, the key or signature is weak, or your CAA records don't allow its issuer. |
| Couldn’t connect | The check couldn't reach the endpoint to look at the certificate. This is a warning about the connection, not a verdict on the certificate. |
| Paused | Checks are turned off for this certificate; it keeps its last result. |
Certificate alert event
Section titled “Certificate alert event”| Status | Meaning |
|---|---|
| Expiring soon | The certificate expires within the largest warning threshold of its check profile. Choose which events alert you under Alert me when in the certificate check profile. |
| Expired | The expiry date has passed. |
| Valid again | The previous check was expiring soon, expired, not trusted or couldn't connect, and this one is valid. |
| Name doesn’t match | The names on the certificate don't cover the host being checked. |
| Chain not trusted | The certificate chain doesn't lead to a trusted certificate authority. |
| Revoked by its issuer | The revocation check reports that the issuer withdrew the certificate. |
| Couldn’t connect | The connection or TLS handshake to the endpoint, or to one of its resolved IPs, failed. |
| Certificate replaced | The certificate's SHA-256 fingerprint differs from the previous check. |
| CAA records changed | Your CAA records don't authorize the certificate's issuer. Despite the name, it fires on that mismatch, not on every change to the records. |
| Weak signature | The signature algorithm or key strength is below modern thresholds: SHA-256 or stronger signatures, at least RSA 2048-bit or ECDSA P-256 keys. |
| Servers show different certificates | The host's resolved IPs served different certificates. It needs a check profile that checks every resolved IP. |
Certificate grade
Section titled “Certificate grade”| Status | Meaning |
|---|---|
| A+ | A score of 95 or more with HSTS seen on the endpoint. Each certificate starts at 100 and loses points for near expiry, a weak key or signature, a CAA mismatch, servers that disagree or don't answer, and old TLS versions or ciphers; HSTS adds 3. |
| A | 90 or more (95 or more without HSTS). |
| B | 80 to 89. |
| C | 65 to 79. |
| D | 50 to 64. |
| F | Below 50, or a hard failure: no usable certificate, expired, chain not trusted, name mismatch, or revoked. |
| No grade yet | No check has graded the certificate yet. |
Certificate agent status
Section titled “Certificate agent status”| Status | Meaning |
|---|---|
| Waiting for first contact | The agent was created but hasn't asked HostRepute for work yet. |
| Online | The agent has contacted HostRepute, to ask for work or send a result, and hasn't gone 15 minutes without contact since. |
| Not heard from | No contact for 15 minutes. HostRepute alerts your channels, and alerts again when the agent is back online. |
| Revoked | You revoked the agent: its token stops working, and the certificates it checks are paused until you move them to another check profile. |
Uptime check status
Section titled “Uptime check status”| Status | Meaning |
|---|---|
| Not checked yet | No uptime check has finished yet. |
| Up | The endpoint answered as expected (an HTTP check wants the status you set, or any 2xx or 3xx, and the keyword when you set one) faster than Slow after, 2,000 ms by default. |
| Slow | It answered as expected but took at least the Slow after time. Like down, it counts toward the failed checks in a row and opens an outage; public status pages call it Degraded. |
| Down | It couldn't be reached, timed out, returned an unexpected status, or failed the keyword check, for the set number of checks in a row (2 by default). While confirming, it's rechecked after 45 seconds. |
| Paused | Checks are turned off; it keeps its last result. |
Uptime outage status
Section titled “Uptime outage status”| Status | Meaning |
|---|---|
| Down | A confirmed outage: the endpoint was down for the set number of checks in a row. It starts at the first failed check. |
| Slow | A confirmed slow period. An outage that turns from slow to down, or back, changes its badge but stays one outage. |
| Ongoing | The outage hasn't ended. It ends when a check comes back up, and then shows how long it lasted. |
Domain registration status
Section titled “Domain registration status”| Status | Meaning |
|---|---|
| Not checked yet | No WHOIS check has finished yet. Checks run every 24 hours. |
| Registered | WHOIS shows an expiry date further away than the largest warning threshold (30 days by default). |
| Expiring soon | The registration expires within the largest warning threshold. HostRepute alerts you then and again as each smaller threshold is reached (30, 14 and 7 days by default). |
| Expired | The expiry date in WHOIS has passed. |
| Expiry date unknown | WHOIS answered but showed no expiry date, so HostRepute can't warn before the domain lapses. A WHOIS server that doesn't answer or limits the lookup is retried instead. |
| Paused | Checks are turned off; it keeps its last result. |
Google Postmaster and Microsoft SNDS connection status
Section titled “Google Postmaster and Microsoft SNDS connection status”| Status | Meaning |
|---|---|
| Connected | Google Postmaster: a Google account is connected and the last sync didn't fail. Microsoft SNDS: a Microsoft sign-in or Data Access links are set up and the last sync didn't fail. |
| Syncing | A sync with Google or Microsoft is running now. |
| Needs attention | The stored sign-in stopped working and you need to reconnect, or the last sync failed. For Google Postmaster it also shows when only some domains synced. |
| Not connected | No Google account is connected yet (Google Postmaster), or no Microsoft sign-in or Data Access links are set (Microsoft SNDS), so nothing syncs. |
| Paused | Connected, but turned off, so nothing new is read until you turn it back on. |
Google Postmaster domain status
Section titled “Google Postmaster domain status”| Status | Meaning |
|---|---|
| Monitoring | HostRepute reads this domain's Gmail data on each sync. |
| Sync problem | The last sync of this domain returned an error, shown on the domain's row. |
| Paused: plan limit | Your plan monitors a set number of Postmaster domains at a time, so this one was paused. The domain's own page shows Plan limit. |
| Gone from Postmaster Tools | The domain is no longer in the connected Google account's Postmaster Tools. The domain's own page shows Removed at source. |
| Paused | Monitoring was turned off for this domain. The domain's own page shows Deactivated. |
| Pending verification | You added the domain in HostRepute, which is waiting for the DNS TXT record that proves you own it. The verification card shows Waiting for DNS record. |
| Verifying | HostRepute is looking for the DNS record and asking Google to confirm it, retrying on its own for up to 72 hours. The verification card shows Checking DNS. |
| Verified | Google confirmed you own the domain; its data appears after the next sync. |
| Verification failed | Google rejected the verification, or the record wasn't found within 72 hours. Check it's published exactly as shown, then try again. |
| Verified at Google | Google's own record says ownership of the domain is verified. |
| Not verified at Google | Google says ownership isn't verified, so it shares no numbers until you prove you own the domain with a DNS record. |
| No data access | Google shares no statistics or compliance data for this domain with the connected account, because ownership isn't verified yet or the account has no access to it. |
| Compliant | Gmail's verdict: the domain meets Gmail's sender requirements. Each requirement in the checklist also shows Compliant or Needs work. |
| Needs work | Gmail's verdict: one or more sender requirements aren't met. HostRepute alerts your channels when a requirement needs work. |
| Not enough data | Gmail hasn't given a verdict yet, for example because there's too little mail from the domain or no data access. |
| Owner | The connected Google account verified the domain and has full control, including who has access. |
| Admin | The account sees all dashboards and can add or remove Readers and Admins. |
| Reader | The account sees dashboards and statistics only. |
| No access | The domain is listed in Postmaster Tools, but the account can't see any of its data. |
Microsoft SNDS IP status and filter result
Section titled “Microsoft SNDS IP status and filter result”| Status | Meaning |
|---|---|
| Mostly clean (green) | Microsoft's spam filter result for the IP's mail that day: mostly clean. |
| Mixed (yellow) | Microsoft's filters treated part of the IP's mail as spam that day. A change from green to yellow sends a filter result alert and lowers the Microsoft SNDS part of the reputation score. |
| Mostly spam (red) | Microsoft's filters treated most of the IP's mail as spam that day. A change to red from any other result sends a filter result alert and lowers the score more than yellow. |
| No result | SNDS gave no filter result for that IP and day. |
| Blocked | Microsoft reported it blocks mail from this IP or range. Each new problem alerts your channels and, while it isn't resolved, lowers the Microsoft SNDS part of the reputation score; Resolved shows when it cleared. |
| Junked | Microsoft reported it sends this IP's mail to junk. |
| Bot | Microsoft's status for the IP reports bot activity. It weighs on the score as heavily as a block. |
| Unknown | Microsoft reported a problem HostRepute couldn't classify as blocked, junked or bot. |
Yahoo Sender Hub setup stage
Section titled “Yahoo Sender Hub setup stage”| Status | Meaning |
|---|---|
| Setup Pending | Next step: add the domain in Yahoo Sender Hub. HostRepute doesn't connect to Yahoo; you move the stage forward yourself after each step in Yahoo's portal. |
| Domain Verified | You published the DNS TXT record Yahoo gave you and confirmed it in Yahoo's portal. Next step: join the Complaint Feedback Loop. |
| Enrolled in CFL | The verified domain is enrolled in Yahoo's Complaint Feedback Loop (CFL), so Yahoo tells you about spam complaints. Setup is complete. |
ESP connection status
Section titled “ESP connection status”| Status | Meaning |
|---|---|
| Connected | The API key works and the last sync didn't fail. |
| Syncing | A sync with the provider is running now. |
| Needs attention | The last sync failed, which usually means the API key changed or lost access. Update the key, then sync again. |
| Paused | Keep syncing is off, so nothing new is read from the provider. Only active connections count toward your plan. |
Status page state
Section titled “Status page state”| Status | Meaning |
|---|---|
| Live | Published and included in your plan, so anyone with the link can see it. Search engines are asked not to list it. |
| Draft | Not published, so the link doesn't open. Turn on Publish this page and save to share it. |
| Paused | HostRepute paused it because your plan no longer includes status pages or you have more pages than it allows, so the link doesn't open. It's published again when the plan allows it. |
| Not on your plan | Your plan doesn't include this page, so the link doesn't open. |
Status page status
Section titled “Status page status”| Status | Meaning |
|---|---|
| Operational | Every published domain or IP has a completed scan and a reputation score, and nothing on it is degraded or an incident. The page as a whole shows the worst status of its domains and IPs. |
| Degraded | No incident, but a certificate is expiring soon, email authentication is failing or needs work, uptime is slow, or the reputation score is below 75. |
| Incident | The domain or IP is on a blocklist, its uptime check is down, its latest blocklist scan failed, or its certificate is expired, not trusted or couldn't connect. |
| Pending | A domain or IP has no completed scan or no reputation score yet, or the page has no published domains or IPs. |
Status page event
Section titled “Status page event”| Status | Meaning |
|---|---|
| Critical | The page's overall status became Incident. Subscribers get an email. |
| Warning | The page's overall status became Degraded. Subscribers get an email. |
| Recovered | The overall status went back to Operational from Degraded or Incident. Open events are marked resolved, and subscribers get an email. |
| Info | Any other change of the overall status, such as to Pending or from Pending to Operational. Subscribers aren't emailed. |
Status page subscriber
Section titled “Status page subscriber”| Status | Meaning |
|---|---|
| Subscribed | Confirmed their email address, so they get an email for every Critical, Warning and Recovered event. |
| Not confirmed | Subscribed on the page but hasn't confirmed from the email yet, so they get no updates. |
| Unsubscribed | Turned updates off from an update email. Subscribing on the page again sends a new confirmation email. |
Scheduled report delivery status
Section titled “Scheduled report delivery status”| Status | Meaning |
|---|---|
| Sending | The report was built and is being emailed to its recipients. |
| Sent | Every recipient was sent the report. |
| Partly sent | Some recipients got it and some couldn't be emailed; the error lists the ones that failed. |
| Skipped: nothing changed | Only send when something changes is on and no domain or IP was listed or removed during the period, so nothing was sent. Test sends are never skipped. |
| Failed | No recipient could be emailed, or the report has no valid recipients. |
| Paused | The report is turned off, so no next report is scheduled. |
Campaign preflight status
Section titled “Campaign preflight status”| Status | Meaning |
|---|---|
| Checking | The check is running; it usually takes less than a minute. |
| Checked | Every part of the check ran. |
| Partly checked | Some parts didn't run, for example authentication alignment or spam scoring, so the result may miss problems. What did run is shown. |
| Couldn’t check | The check stopped: the email couldn't be read, it took too long, or something failed on HostRepute's side. The credit is refunded. |
Campaign preflight verdict
Section titled “Campaign preflight verdict”| Status | Meaning |
|---|---|
| Fix before sending | At least one high-severity finding could send the email to spam or get it rejected. |
| Worth fixing | No high-severity finding, but at least one medium one could hurt delivery. |
| Looks good | No high- or medium-severity findings; minor findings and notes may still be listed. |
Campaign preflight finding severity
Section titled “Campaign preflight finding severity”| Status | Meaning |
|---|---|
| Fix before sending | High severity: a problem that could send the email to spam or get it rejected, such as misaligned DKIM, an image-only message or a link whose text shows a different domain. |
| Worth fixing | Medium severity: something that could hurt delivery but doesn't block sending. |
| Minor | Low severity: a small improvement. |
| Note | Informational: checked, nothing to change. |
Credit transaction type
Section titled “Credit transaction type”| Status | Meaning |
|---|---|
| Purchase | Credits from a credit package you bought (purchase). Billing's Credit history lists each transaction by its description; the MCP server returns the type value. |
| Auto Recharge | Credits from a package paid through an auto-recharge payment link (auto_recharge). |
| Usage | Credits spent on a paid action, such as a manual blocklist scan, a certificate check, an email authentication check, a campaign preflight or an AI assistant answer (usage). |
| Refund | Credits returned because a paid action failed or didn't run, for example a manual scan that failed (refund). |
| Adjustment | A manual change to the balance by HostRepute staff, up or down (adjustment). |
| Bonus | Extra credits granted by HostRepute staff (bonus). |
| Chargeback | Credits taken back after Paddle refunded or charged back the purchase; the balance can go below zero (chargeback). |
| Referral | Credits earned through the referral program (referral). |
Plan status
Section titled “Plan status”| Status | Meaning |
|---|---|
| Trial | The team is on its Owner's 14-day trial, with the limits of the Professional plan. The card shows how many days are left. Nothing is billed until the Owner subscribes. |
| Active | The team pays for this plan through Paddle, monthly or yearly, and the subscription renews by itself. |
| Cancellation scheduled | The subscription is cancelled but stays active until the end date the card shows; after that the team has no plan. Resume subscription undoes the cancellation until then. |
| Complimentary | HostRepute gave the team this plan without charge, until the date the card shows or with no end date. If the team also pays for a plan, the higher of the two applies. |
| No plan | The trial ended or the subscription was cancelled. Nothing is checked and no alerts are sent until the Owner chooses a plan; the team's domains, IPs and settings are kept. |
Referral status
Section titled “Referral status”| Status | Meaning |
|---|---|
| Pending | The team signed up through your link but hasn't paid yet. Waiting to pay counts these. |
| Qualified | The team made its first payment, for a plan or for credits, and your team and theirs each got their referral credits. First payment shows when. |
| Rejected | The team paid, but the referral earns no credits: the team has the same Owner as yours, or your team had already reached its limit of referrals that earn credits. |
Single sign-on status
Section titled “Single sign-on status”| Status | Meaning |
|---|---|
| Not configured | The identity provider settings aren't complete, so single sign-on can't be turned on or tested yet. Fill in the connection and choose Save connection. |
| Disabled | The connection is saved, but single sign-on is off. Members sign in with a password, a passkey or a social sign-in. |
| Enabled | People with an email on a verified domain can sign in through the identity provider, and every other sign-in method still works. |
| Enforced | Single sign-on is on, set to Required, and its connection test passed. Everyone with an email on a verified domain must sign in through the identity provider, except the team's Owner. |
Single sign-on domain status
Section titled “Single sign-on domain status”| Status | Meaning |
|---|---|
| Pending | The domain is added, but HostRepute hasn't found its TXT record at _hostrepute-sso.<domain> yet. Publish the record, then choose Verify. |
| Verified | HostRepute found the TXT record. People with an email on this domain can sign in through single sign-on, and enforcement applies to them. |
API token status
Section titled “API token status”| Status | Meaning |
|---|---|
| Active | The token works. It has no expiry date, or its expiry date hasn't passed yet. |
| Expired | The token's expiry date has passed, and the API answers 401 to it. It stays in the list until you revoke it. |
Related
Section titled “Related”- How HostRepute works explains scans, their results and the reputation score.
- Blocklists HostRepute checks lists the blocklists behind each scan result.
- Email authentication checks describes each check that produces an email authentication result.
- Webhook events shows the payloads that carry these statuses.
- Glossary defines a scan and the other portal terms.

