magnum.com — domain analysis
magnum.com is a live website built on WordPress, registered in 1995, served from Austin, United States. It has a valid HTTPS certificate, 0 of 6 common security headers, 1 tracking script.
What is magnum.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- magnum ×3
Does magnum.com publish the usual trust pages?
Found: about, contact. Not found at the usual addresses:
privacy, terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does magnum.com compare with other domains analysed here?
Measured against the 77 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 55% of them (median 662ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 95% of them |
Related domains in this index
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was magnum.com registered?
magnum.com was registered on 17 January 1995, which makes it about 31 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 18 January 2027.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 17 January 1995 |
|---|---|
| Expires | 18 January 2027 |
| Registrar | GoDaddy.com, LLC |
| Registry status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
Where is magnum.com hosted?
The first address resolves to infrastructure in Austin, United States.
The network is operated by WPEngine, Inc. (AS209242 Cloudflare London, LLC).
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 magnum.com running on?
magnum.com exposes 5 identifiable technologies: WordPress, jQuery, Cloudflare, Google Analytics, X-Powered-By: WP Engine.
WordPress is identifiable from its asset paths, so the platform is public knowledge regardless of whether the version is hidden. That matters mainly for patching discipline: known-platform sites are scanned automatically and constantly.
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.
Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.
- WordPress
- jQuery
- Cloudflare
- Google Analytics
- X-Powered-By: WP Engine
The page declares a generator of Site Kit by Google 1.188.0.
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 630ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 185KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 189,555 bytes |
| Declared language | en-US |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is only 6 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.
There are 2 H1 headings. One is conventional; several dilute the signal about what the page is primarily about.
All 2 images on the homepage have alt attributes.
| Title | Magnum (6 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | Forgot Password? (2 on the page) |
| Canonical | https://www.magnum.com/ |
| Open Graph title | not set |
| Headings / images | 2 H2s, 2 images (0 without alt text) |
Is magnum.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-24, which is 50 days from the date of this check. It covers
1 hostname.
- magnum.com
The certificate has 50 days left to run.
It covers 1 hostname, 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.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
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 | no | — |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for magnum.com?
| IP addresses | 141.193.213.11, 141.193.213.10 |
|---|---|
| Reverse DNS | 141.193.213.11, 141.193.213.10 |
| Name servers | ns48.domaincontrol.com, ns47.domaincontrol.com |
| Mail (MX) | magnum-com.mail.protection.outlook.com (pri 0) |
| SPF | v=spf1 include:spf.protection.outlook.com -all |
| TXT records | 2 |
magnum.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 141.193.213.11, 141.193.213.10, which usually names the hosting provider.
Who runs DNS and mail for magnum.com?
DNS is operated by GoDaddy rather than self-hosted name servers.
Mail is handled by Microsoft 365.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about magnum.com?
6 of 6 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.
Can magnum.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 130 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.magnum.com/wp-sitemap.xml
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 magnum.com load from third parties?
The homepage pulls resources from 3 third-party hosts (fonts.googleapis.com, googletagmanager.com, magnumfund.wpengine.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does magnum.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both magnum.com and www.magnum.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can magnum.com be crawled?
A sitemap index is served at https://www.magnum.com/wp-sitemap.xml listing 5 entries.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does magnum.com run?
1 tracking script detected: Google Analytics.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does magnum.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?
2 images 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.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 11 external stylesheets and 6 external scripts, with 1 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Responses carry Cloudflare and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is magnum.com accessible and current?
The page uses 1 landmark element and 11 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index magnum.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 3 internal and 1 external link across 1 outside host.
Visible text is only 0.1% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is magnum.com delivered?
The HTML is served with Cache-Control: max-age=600, must-revalidate.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
Frequently asked questions
Does magnum.com set the usual HTTP security headers?
It sets 0 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does magnum.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 magnum.com built with?
The homepage exposes these fingerprints: WordPress, jQuery, Cloudflare, Google Analytics, X-Powered-By: WP Engine. 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 magnum.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 →
The weekly edition
Three or four things explained, in plain language, with the sources. One email a week. No spam, no algorithm in between.
