levis.com blocks automated analysis, answering with access denied page 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 access denied page 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 levis.com compare with other domains analysed here?
Measured against the 81 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 78% of them (median 491ms) |
|---|---|
| Domain age | Older than 76% of them |
Related domains in this index
Other analysed domains served from the same country:
When was levis.com registered?
levis.com was registered on 16 October 1996, which makes it about 29 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 MarkMonitor Inc..
Registration runs until 15 October 2028.
The domain carries 3 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 16 October 1996 |
|---|---|
| Expires | 15 October 2028 |
| Registrar | MarkMonitor Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited |
Where is levis.com hosted?
The first address resolves to infrastructure in Lehi, United States.
The network is operated by Vercara, LLC (AS12008 Vercara, 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 levis.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of levis.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
HTTP.
At 184ms to first byte this response is fast for a homepage measured from a single European location.
No compression is applied to the HTML. Enabling gzip or brotli usually cuts transfer size by around two thirds at no cost to the server.
| Server header | AkamaiGHost |
|---|---|
| Compression | none |
| Page size | 387 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 levis.com served over a valid certificate?
No TLS certificate could be read on port 443. The site may serve HTTP only, or block direct TLS connections.
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 levis.com?
| IP addresses | 204.74.99.100 |
|---|---|
| Reverse DNS | crs.ultradns.net |
| Name servers | nans2.levi.com, nans1.levi.com |
| Mail (MX) | no mail records |
| SPF | v=spf1 -all |
| TXT records | 1 |
levis.com resolves to a single address, so there is no DNS-level redundancy.
No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to crs.ultradns.net, which usually names the hosting provider.
Can levis.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
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?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does levis.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
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 levis.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 →