introduced.app was registered on 24 Jun 2015. 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.
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 introduced.app. Refresh the analysis to check again.
64 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| introduced.social | Other extension | 22 Oct 2026 | Checking… | Report → |
| introduced.info | Other extension | 5 Oct 2026 | Checking… | Report → |
| introduce.careers | Typo | 12 Oct 2026 | Checking… | Report → |
| introduce.uk.com | Typo | 5 Oct 2026 | Checking… | Report → |
| introduce.page | Typo | 3 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is introduced.app’s name taken on other extensions?
| Host | Mail server | TTL |
|---|---|---|
| introduced.app | 0 mx1.spacemail.com | 1200 |
| introduced.app | 0 mx2.spacemail.com | 1200 |
| Host | Name server | TTL |
|---|---|---|
| introduced.app | launch1.spaceship.net | 1800 |
| introduced.app | launch2.spaceship.net | 1800 |
| Host | Text | TTL |
|---|---|---|
| introduced.app | "v=spf1 include:spf.spacemail.com ~all" | 1200 |
| Host | Start of authority | TTL |
|---|---|---|
| introduced.app | launch1.spaceship.net support.spaceship.com 1735945004 43200 3600 604800 3600 | 1800 |
| Host | Value | TTL |
|---|---|---|
| introduced.app | 256 3 13 tlTx8XJQWHXa3SSVaQgQdLz5wS9w/WFr98LjXqNOkVQGejnmm7Bu2ve6Lds467ouSlWVSJaQ+u9TugcK0nMTXQ== | 3600 |
| introduced.app | 257 3 13 FBfSml0cS/y9eY/dI5608aiZCbf8y/GuTxlNT8K73Ur8jU74dF9JF5rjzM+18U+UVzt5HUwKzVZS5Y8lEEc0gw== | 3600 |
No reviews yet. Used introduced.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.
introduced.app has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
introduced.app was registered on 24 Jun 2015, making it 11 years old. See Overview →
Raw registry data for introduced.app. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: domain: APP organisation: Charleston Road Registry Inc. address: 1600 Amphitheatre Parkway address: Mountain View CA 94043 address: United States of America (the) contact: administrative name: TLD Admin organisation: Google Inc. address: 111 8th Avenue address: New York NY 10011 address: United States of America (the) phone: +1 404 978 8419 fax-no: +1 650 492 5631 e-mail: [email protected] contact: technical name: TLD Engineering organisation: Google Inc address: 76 Ninth Avenue, 4th Floor address: New York NY 10011 address: United States of America (the) phone: +1 404 978 8419 fax-no: +1 650 492 5631 e-mail: [email protected] nserver: NS-TLD1.CHARLESTONROADREGISTRY.COM 2001:4860:4802:32:0:0:0:69 216.239.32.105 nserver: NS-TLD2.CHARLESTONROADREGISTRY.COM 2001:4860:4802:34:0:0:0:69 216.239.34.105 nserver: NS-TLD3.CHARLESTONROADREGISTRY.COM 2001:4860:4802:36:0:0:0:69 216.239.36.105 nserver: NS-TLD4.CHARLESTONROADREGISTRY.COM 2001:4860:4802:38:0:0:0:69 216.239.38.105 nserver: NS-TLD5.CHARLESTONROADREGISTRY.COM 2001:4860:4805:0:0:0:0:69 216.239.60.105 ds-rdata: 23684 8 2 3a5cc8a31e02c94aba6461912fabb7e9f5e34957bb6114a55a864d96aec31836 whois: status: ACTIVE remarks: Registration information: https://www.registry.google created: 2015-06-25 changed: 2025-04-11 source: IANA
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with introduced.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.