aegaming.app was registered on 25 Jun 2015 and is hosted on AS16276 in France. We couldn't read an SSL certificate for it when we last analysed it.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
1 of 5 protections set up
Lists the servers allowed to send email for this domain.
v=spf1 include:mx.ovh.com -allNo key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
0 of 6 recommended headers
The page is served over plain HTTP, so HTTPS can’t be enforced.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows, and whether it publishes an llms.txt.
llms.txt is an optional guide some sites publish for AI assistants — it is not a ranking factor.
Pages and files that show who runs the site and how it handles data.
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 aegaming.app. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
35 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| eagaming.online | Typo | 8 Oct 2026 | Checking… | Report → |
| asgaming.com.tw | Typo | 1 Oct 2026 | Checking… | Report → |
| adgaming.biz | Typo | 16 Sept 2026 | Checking… | Report → |
| wegaming.casino | Typo | 3 Sept 2026 | Checking… | Report → |
| argaming.online | Typo | 1 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is aegaming.app’s name taken on other extensions?
Every IP address aegaming.app resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| aegaming.app | 213.186.33.5 | 3600 |
| Host | Mail server | TTL |
|---|---|---|
| aegaming.app | 1 mx1.mail.ovh.net | 3600 |
| aegaming.app | 5 mx2.mail.ovh.net | 3600 |
| aegaming.app | 100 mx3.mail.ovh.net | 3600 |
| Host | Name server | TTL |
|---|---|---|
| aegaming.app | dns106.ovh.net | 3600 |
| aegaming.app | ns106.ovh.net | 3600 |
| Host | Text | TTL |
|---|---|---|
| aegaming.app | "1|www.aegaming.app" | 3600 |
| aegaming.app | "v=spf1 include:mx.ovh.com -all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| aegaming.app | dns106.ovh.net tech.ovh.net 2092090208 86400 3600 3600000 60 | 3600 |
| Host | Value | TTL |
|---|---|---|
| aegaming.app | 256 3 8 AwEAAdbE+tVbTTATLHUcWksCYDo4/GpuOxINEqHo/atPau9/aBCzHxT6KRr/JtDmjbAxdY8dY4rA0OPEa50YSPf48i5hwZCkamOvIyy4xuKS3mNGJ5w2690FA1sPNIPWDR7rKNZSXXgZClnbj7HT++8co5FlXt7KFUxRSOKampqD4LP9 | 3600 |
| aegaming.app | 257 3 8 AwEAAcB6LpL7aPNgCgeo9NnKlPSLYXvHw2KuFAZRHGDxNiVSUCO7wtMqodhRJlXr76fOuuMk2V0Y1DRyN4RY0df6MbkR0/NiacbWcVnRufXcLIfcp+OiudtNV5ttLe7E8cy2nUiNkM5uu7if9dzdO33TMHFAi63bZRGNSilnqNzqfckgQ2aTXxPCcK5iP11hPsU/NBeYGWzJpBdNrLOd7ROJDy6sb0BDqvUpn8S3qqrEswV8ePpEe0KwsD73vDu3njeli7OWop3VhHvUnPSutAeY6KBRrbKfo2bIJTpuhaVDJTGDA3f0z0Y6cU6drk1YRkQ0UNmtjit2HlrMBN88aV7b/mU= | 3600 |
Other domains served from 213.186.33.5. Normal for shared hosting and CDNs.
No reviews yet. Used aegaming.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.
aegaming.app has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
aegaming.app was registered on 25 Jun 2015, making it 11 years old. See Overview →
aegaming.app is served from 1 IP address, mainly on AS16276 in France. See Hosting →
Raw registry data for aegaming.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 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
The first response from http://www.aegaming.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 aegaming.app. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, http://www.aegaming.app/
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.
No changes seen since we started recording on 3 Nov 2026.