Skip to content
Thursday, 19 November 2026
WorldGeek.net

Tech, gaming, anime, sci-fi — independent global geek publication

Edition №323 · 19 Nov 2026 · Multi-vertical Subscribe
Independent · Source-cited · 7-Editor Team · No Piracy · No Paid Coverage

Article

wego.com — domain analysis

wego.com is a live website, registered in 1998, served from Toronto, Canada. It has a valid HTTPS certificate, 1 of 6 common security headers. 200HTTP status 571msResponse time 10Words on…

wego.com — domain analysis

wego.com is a live website, registered in 1998, served from Toronto, Canada. It has a valid HTTPS certificate, 1 of 6 common security headers.

200HTTP status
571msResponse time
10Words on the homepage
1/6Security headers set

Does wego.com publish the usual trust pages?

None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

How does wego.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 37% of them
(median 419ms)
Security headers More than 47% of them
Domain age Older than 67% 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.

Analysed domains built on a similar stack:

Other analysed domains served from the same country:

When was wego.com registered?

wego.com was registered on 16 November 1998, which makes it about 27 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is GoDaddy.com, LLC.

Registration runs until 15 November 2034.

The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.

Registered 16 November 1998
Expires 15 November 2034
Registrar GoDaddy.com, LLC
Registry status client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited

Where is wego.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 wego.com running on?

wego.com exposes 1 identifiable technology: Cloudflare.

Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.

  • Cloudflare

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

At 571ms to first byte this response is unremarkable for a homepage measured from a single European location.

The HTML weighs 23KB, which is ordinary for a homepage.

The HTML is compressed with gzip.

Server header cloudflare
Compression gzip
Page size 23,818 bytes
Declared language en
Mobile viewport declared

What does the homepage say about itself?

The title is only 4 characters, which is short enough that it probably is not describing the page so much as naming it.

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.

All 1 images on the homepage have alt attributes.

Title Wego (4 chars)
Meta description — none — (0 chars)
H1 — none — (0 on the page)
Canonical not set
Open Graph title not set
Headings / images 0 H2s, 1 images (0 without alt text)

Is wego.com served over a valid certificate?

The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-03, which is 59 days from the date of this check. It covers
3 hostnames.

  • wego.com
  • *.wego.com
  • *.internal.wego.com

The certificate has 59 days left to run.

Which security headers does it set?

1 of 6 are set (HSTS). Absent: Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.

Header Set Value
HSTS yes max-age=2592000
Content Security Policy no —
X-Content-Type-Options no —
X-Frame-Options no —
Referrer-Policy no —
Permissions-Policy no —

How is DNS configured for wego.com?

IP addresses 104.18.244.115, 104.18.245.115, 104.18.242.115, 104.18.241.115, 104.18.243.115, 2606:4700::6812:f473, 2606:4700::6812:f373, 2606:4700::6812:f173, 2606:4700::6812:f573, 2606:4700::6812:f273
Reverse DNS 104.18.244.115, 104.18.245.115
Name servers dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net
Mail (MX) alt2.aspmx.l.google.com (pri 5), alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), aspmx.l.google.com (pri 1), alt1.aspmx.l.google.com (pri 5)
SPF v=spf1 ip4:151.193.224.244 ip4:151.193.224.232 ip4:151.193.224.245 ip4:151.193.224.233 ip4:151.193.65.92 ip4:151.193.65.93 include:amazonses.com include:_spf.google.com +a +mx ~all
TXT records 48

wego.com resolves to 10 addresses, which indicates load balancing or a CDN rather than a single origin server.

Mail is handled by 5 exchangers.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 104.18.244.115, 104.18.245.115, which usually names the hosting provider.

Who runs DNS and mail for wego.com?

DNS is operated by NS1 rather than self-hosted name servers.

Mail is handled by Google Workspace.

The domain publishes AAAA records and accepts connections over IPv6.

What else is worth noting about wego.com?

All 1 externally hosted scripts carry subresource integrity hashes, so a compromised CDN could not silently swap them.

Can wego.com be spoofed in email?

DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.

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 else does wego.com publish?

An ads.txt file is published with 2 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.

An app-ads.txt file is also published, which indicates mobile app inventory alongside the website.

What does robots.txt allow?

robots.txt is 1,374 bytes and names
1 user-agent group.

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.

What does wego.com load from third parties?

The homepage pulls resources from 2 third-party hosts (fonts.googleapis.com, static.cloudflareinsights.com). Each one sees the visitor IP and user agent on every page load.

1 cookie is set before any interaction (__cf_bm).

Cookie Secure HttpOnly SameSite
__cf_bm yes yes none

Does wego.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

The www address redirects to https://www.wegoreise.de, so the site settles on one canonical hostname.

How easily can wego.com be crawled?

No readable sitemap was found, so crawlers have to discover every page by following links.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does wego.com run?

No analytics or advertising trackers were detected on the homepage of wego.com, which is unusual for a commercial site.

How does wego.com look when shared?

No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.

How are images, fonts and scripts handled?

1 image on the homepage, 0 of them lazy-loaded (0%).

All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.

No srcset attributes are used, so every device is served the same image size regardless of screen.

Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.

The page pulls 2 external stylesheets and 3 external scripts, with 2 carrying defer or async.

Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.

Is wego.com accessible and current?

The page uses 1 landmark element and 3 ARIA attributes.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index wego.com?

Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.

No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.

The homepage carries 1 internal and 0 external links across 0 outside hosts.

Visible text is only 0.2% of the HTML, which indicates the page is assembled in the browser rather than served as content.

How is wego.com delivered?

The HTML is served with Cache-Control: public, s-maxage=604800, stale-while-revalidate=3600.

HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.

A web app manifest is declared, so the site is installable as a progressive web app.

The TLS certificate also covers 1 subdomain: internal.wego.com.

  • internal.wego.com

Frequently asked questions

Does wego.com set the usual HTTP security headers?

It sets 1 of 6. The ones not present are: Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does wego.com allow AI crawlers?

robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.

What is wego.com built with?

The homepage exposes these fingerprints: Cloudflare. A site behind a CDN or rendered server-side may use more than it reveals.

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 wego.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 →

wg_admin

WorldGeek Editorial

Writer at WorldGeek.

More from this author →