We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
The WOT community hasn't rated this domain yet.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed incidentreporting.us. Refresh the analysis to check again.
4 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| incidentreporting.app | Other extension | 21 Aug 2026 | Checking… | Report → |
| spotincidentreporting.com | Keyword added | 20 Oct 2026 | Checking… | Report → |
| cyberincidentreporting.com | Keyword added | 25 Aug 2026 | Checking… | Report → |
| philcstincidentreporting.com | Keyword added | 24 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is incidentreporting.us’s name taken on other extensions?
No reviews yet. Used incidentreporting.us? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with incidentreporting.us. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.