budsguns.com is a live website, registered in 2004, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 1 of 6 common security headers.
What is budsguns.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:
- budsguns ×2
- coming ×2
- soon ×2
Does budsguns.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 budsguns.com compare with other domains analysed here?
Measured against the 74 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 96% of them (median 463ms) |
|---|---|
| Security headers | More than 35% of them |
| Domain age | Older than 61% of them |
Related domains in this index
Analysed domains sharing the same network (AS63949 Akamai Connected Cloud):
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:
- honda.com.tr
- ketua.com
- razzsuman.com
- savana.com
- simplefastloans.com
- sinsay.com
- swagbucks.com
- toasttab.com
When was budsguns.com registered?
budsguns.com was registered on 10 September 2004, which makes it about 22 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 Above.com Pty Ltd..
Registration runs until 10 September 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 10 September 2004 |
|---|---|
| Expires | 10 September 2027 |
| Registrar | Above.com Pty Ltd. |
| Registry status | client transfer prohibited |
Where is budsguns.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by Linode (AS63949 Akamai Connected Cloud).
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 budsguns.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of budsguns.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 200 over
HTTP.
At 53ms to first byte this response is fast for a homepage measured from a single European location.
At 1KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | openresty/1.29.2.5 |
|---|---|
| Compression | gzip |
| Page size | 1,387 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 26 characters, inside the range that displays without truncation.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
| Title | budsguns.com – Coming Soon (26 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | budsguns.com (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is budsguns.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-14, which is 40 days from the date of this check. It covers
2 hostnames.
- *.budsguns.com
- budsguns.com
The certificate has 40 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?
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=0; includeSubDomains; preload |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for budsguns.com?
| IP addresses | 139.162.181.76, 172.104.203.186, 172.104.251.198, 139.162.174.209, 172.104.149.86, 2a01:7e01::f03c:95ff:feed:783e, 2a01:7e01::f03c:95ff:feeb:9d4b, 2a01:7e01::2000:dff:fec1:5cdb, 2a01:7e01::f03c:95ff:fe00:2692, 2a01:7e01::f03c:95ff:fe91:5d91 |
|---|---|
| Reverse DNS | 139-162-181-76.ip.linodeusercontent.com, 172-104-203-186.ip.linodeusercontent.com |
| Name servers | anan.ns.giantpanda.com, po.ns.giantpanda.com |
| Mail (MX) | mail.mailerhost.net (pri 1) |
| SPF | v=spf1 ip6:fd43:c0d1:c090::/48 -all |
| TXT records | 1 |
budsguns.com resolves to 10 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 139-162-181-76.ip.linodeusercontent.com, 172-104-203-186.ip.linodeusercontent.com, which usually names the hosting provider.
Who runs DNS and mail for budsguns.com?
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
The domain publishes AAAA records and accepts connections over IPv6.
Can budsguns.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.
What does budsguns.com load from third parties?
The homepage loads no resources from third-party hosts at all, which is rare and means visiting it tells no other company that you did.
No cookies are set on first load.
Does budsguns.com settle on one address?
Plain HTTP serves the site directly instead of redirecting to HTTPS. That leaves an unencrypted copy reachable and gives search engines two addresses for the same content.
The www hostname does not respond at all, so anyone typing www.budsguns.com reaches nothing.
How easily can budsguns.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
What tracking does budsguns.com run?
No analytics or advertising trackers were detected on the homepage of budsguns.com, which is unusual for a commercial site.
How does budsguns.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?
The page pulls 0 external stylesheets and 0 external scripts, with 0 carrying defer or async.
Is budsguns.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index budsguns.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.
Visible text makes up 5.2% of the HTML.
How is budsguns.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
No favicon is declared in the markup.
Frequently asked questions
Does budsguns.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 budsguns.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 4 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 budsguns.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 4 October 2026.
Analyse another domain →