Skip to content

vag.com — domain analysis

By TechQuiller com Published 1 min read

vag.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.

403HTTP status
752msResponse time
0Words on the homepage
0/6Security headers set

How does vag.com compare with other domains analysed here?

Measured against the 82 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 24% of them
(median 523ms)
Domain age Older than 76% of them

Related domains in this index

Analysed domains sharing the same network (AS16509 Amazon.com, 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 vag.com registered?

vag.com was registered on 11 January 2000, which makes it about 26 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 Dynadot Inc.

Registration runs until 11 January 2027.

The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.

Registered 11 January 2000
Expires 11 January 2027
Registrar Dynadot Inc
Registry status client transfer prohibited

Where is vag.com hosted?

The first address resolves to infrastructure in San Jose, United States.

The network is operated by AWS EC2 (us-west-1) (AS16509 Amazon.com, 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 vag.com running on?

No platform, framework or analytics fingerprints were found in the homepage markup of vag.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 752ms to first byte this response is slow 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,408 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 vag.com served over a valid certificate?

The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-27, which is 52 days from the date of this check. It covers
2 hostnames.

  • *.vag.com
  • vag.com

The certificate has 52 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 vag.com?

IP addresses 54.215.31.113
Reverse DNS ec2-54-215-31-113.us-west-1.compute.amazonaws.com
Name servers ns1.dyna-ns.net, ns2.dyna-ns.net
Mail (MX) no mail records
SPF not published
TXT records 0

vag.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.

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 ec2-54-215-31-113.us-west-1.compute.amazonaws.com, which usually names the hosting provider.

Can vag.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?

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