Article
myapexevent.com — domain analysis
myapexevent.com blocks automated analysis, answering with Cloudflare interstitial instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below. This site blocks automated analysis.…
myapexevent.com blocks automated analysis, answering with Cloudflare interstitial instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis.
It answered our request with Cloudflare interstitial rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.
How does myapexevent.com compare with other domains analysed here?
Measured against the 79 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 89% of them (median 419ms) |
|---|---|
| Domain age | Older than 35% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Other analysed domains served from the same country:
When was myapexevent.com registered?
myapexevent.com was registered on 5 October 2017, which makes it about 8 years old.
The registrar of record is GoDaddy.com, LLC.
Registration runs until 5 October 2027.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 5 October 2017 |
|---|---|
| Expires | 5 October 2027 |
| Registrar | GoDaddy.com, LLC |
| Registry status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
Where is myapexevent.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is myapexevent.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of myapexevent.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 403 over
HTTPS.
At 62ms to first byte this response is fast for a homepage measured from a single European location.
At 5KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 5,555 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is myapexevent.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-12-29, which is 85 days from the date of this check. It covers
2 hostnames.
- *.myapexevent.com
- myapexevent.com
The certificate has 85 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for myapexevent.com?
| IP addresses | 172.67.68.110, 104.26.7.191, 104.26.6.191, 2606:4700:20::ac43:446e, 2606:4700:20::681a:7bf, 2606:4700:20::681a:6bf |
|---|---|
| Reverse DNS | 172.67.68.110, 104.26.7.191 |
| Name servers | cameron.ns.cloudflare.com, veronica.ns.cloudflare.com |
| Mail (MX) | no mail records |
| SPF | not published |
| TXT records | 3 |
myapexevent.com resolves to 6 addresses, which indicates load balancing or a CDN rather than a single origin server.
No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.
No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.
Reverse DNS resolves to 172.67.68.110, 104.26.7.191, which usually names the hosting provider.
Can myapexevent.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 2,358 bytes and names
27 user-agent groups.
It does not blanket-disallow general crawlers.
No sitemap is declared in robots.txt.
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does myapexevent.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own myapexevent.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →