freshalert.app was registered with CloudFlare, Inc. on 11 Nov 2023. Its SSL certificate from "GoDaddy.com expired on 9 Dec 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
3 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| fresh-alert.com | Hyphen added | 29 Oct 2026 | Checking… | Report → |
| freshalerts.xyz | Extra letter | 16 Sept 2026 | Checking… | Report → |
| refreshalerts.xyz | Keyword added | 17 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is freshalert.app’s name taken on other extensions?
Every IP address freshalert.app resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| freshalert.app | 104.21.26.143 | 300 |
| freshalert.app | 172.67.136.128 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| freshalert.app | 2606:4700:3030::ac43:8880 | 300 |
| freshalert.app | 2606:4700:3035::6815:1a8f | 300 |
| Host | Mail server | TTL |
|---|---|---|
| freshalert.app | 30 route1.mx.cloudflare.net | 300 |
| freshalert.app | 80 route2.mx.cloudflare.net | 300 |
| freshalert.app | 97 route3.mx.cloudflare.net | 300 |
| Host | Name server | TTL |
|---|---|---|
| freshalert.app | amit.ns.cloudflare.com | 21600 |
| freshalert.app | zita.ns.cloudflare.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| freshalert.app | "v=spf1 include:_spf.mx.cloudflare.net ~all" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| freshalert.app | amit.ns.cloudflare.com dns.cloudflare.com 2350754471 10000 2400 604800 1800 | 1800 |
Other domains served from 172.67.136.128. Normal for shared hosting and CDNs.
No reviews yet. Used freshalert.app? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
freshalert.app has no community safety rating yet. Its SSL certificate expired on 9 Dec 2024. See Security →
freshalert.app is registered through CloudFlare, Inc. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 11 Nov 2024. See Overview →
freshalert.app was registered on 11 Nov 2023, making it 3 years old. See Overview →
freshalert.app is served from 2 IP addresses, mainly on AS13335. See Hosting →
Raw registry data for freshalert.app. May be redacted by privacy services.
Domain Name: freshalert.app Registry Domain ID: DFE9D7082-APP Registrar WHOIS Server: whois.cloudflare.com Registrar URL: None Updated Date: 2023-11-17T05:02:59Z Creation Date: 2023-11-12T05:02:59Z Registry Expiry Date: 2024-11-12T05:02:59Z Registrar: CloudFlare, Inc. Registrar IANA ID: 1910 Registrar Abuse Contact Email: registrar-abuse@cloudflare.com Registrar Abuse Contact Phone: +1.4153197517 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: ON Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: CA Registrant Phone: REDACTED FOR PRIVACY Registrant Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Billing ID: REDACTED FOR PRIVACY Billing Name: REDACTED FOR PRIVACY Billing Street: REDACTED FOR PRIVACY Billing City: REDACTED FOR PRIVACY Billing State/Province: REDACTED FOR PRIVACY Billing Postal Code: REDACTED FOR PRIVACY Billing Country: REDACTED FOR PRIVACY Billing Phone: REDACTED FOR PRIVACY Billing Email: Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: amit.ns.cloudflare.com Name Server: zita.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2024-09-07T10:30:13Z <<< For more information on Whois status codes, please visit https://icann.org/epp Please query the WHOIS server of the owning registrar identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. You may also request underlying Registrant data via ICANN's RDRS service (https://rdrs.icann.org/). WHOIS information is provided by Charleston Road Registry Inc. (CRR) solely for query-based, informational purposes. By querying our WHOIS database, you are agreeing to comply with these terms (https://www.registry.google/about/whois-disclaimer.html) and acknowledge that your information will be used in accordance with CRR's Privacy Policy (https://www.registry.google/about/privacy.html), so please read those documents carefully. Any information provided is "as is" without any guarantee of accuracy. You may not use such information to (a) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations; (b) enable high volume, automated, electronic processes that access the systems of CRR or any ICANN-Accredited Registrar, except as reasonably necessary to register domain names or modify existing registrations; or (c) engage in or support unlawful behavior. CRR reserves the right to restrict or deny your access to the Whois database, and may modify these terms at any time.
The first response from http://www.freshalert.app, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with freshalert.app. 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.