patron.com describes itself as "Join patron on Bidsy — live auctions and private 1-on-1 chats and video calls with creators.". It was registered in 1996, served from Washington, United States. It has a valid HTTPS certificate, 0 of 6 common security headers.
Does patron.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 patron.com compare with other domains analysed here?
Measured against the 68 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 25% of them (median 408ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 90% of them |
Related domains in this index
Analysed domains sharing the same network (AS396982 Google LLC):
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:
- akool.com
- aquiensigue.com
- bleepmedia.com
- desisexyvideo.com
- getpgoffer.com
- hkyahoo.com
- marry.com
- mcluck.com
When was patron.com registered?
patron.com was registered on 28 April 1996, which makes it about 30 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 Register.com – Network Solutions, LLC.
Registration runs until 29 April 2031.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 28 April 1996 |
|---|---|
| Expires | 29 April 2031 |
| Registrar | Register.com – Network Solutions, LLC |
| Registry status | client transfer prohibited |
Where is patron.com hosted?
The first address resolves to infrastructure in Washington, United States.
The network is operated by Google Cloud (us-east4) (AS396982 Google 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 patron.com running on?
patron.com exposes 1 identifiable technology: X-Powered-By: Express.
- X-Powered-By: Express
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 1055ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 22KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | Apache |
|---|---|
| Compression | gzip |
| Page size | 22,868 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is only 15 characters, which is short enough that it probably is not describing the page so much as naming it.
A meta description of 92 characters is present.
No H1 heading was found, so the page offers no single top-level statement of what it is.
| Title | patron on Bidsy (15 chars) |
|---|---|
| Meta description | Join patron on Bidsy — live auctions and private 1-on-1 chats and video calls with creators. (92 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://bidsy.com/patron |
| Open Graph title | patron on Bidsy |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is patron.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-10-20, which is 15 days from the date of this check. It covers
1 hostname.
- patron.com
The certificate has 15 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 patron.com?
| IP addresses | 34.145.185.31 |
|---|---|
| Reverse DNS | 31.185.145.34.bc.googleusercontent.com |
| Name servers | pdns2.ultradns.net, pdns3.ultradns.org, pdns4.ultradns.org, pdns5.ultradns.info, pdns6.ultradns.co.uk, pdns1.ultradns.net |
| Mail (MX) | no mail records |
| SPF | not published |
| TXT records | 0 |
patron.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 31.185.145.34.bc.googleusercontent.com, which usually names the hosting provider.
Who runs DNS and mail for patron.com?
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about patron.com?
The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.
Can patron.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 37 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 patron.com load from third parties?
The homepage pulls resources from 3 third-party hosts (bidsy.com, fonts.googleapis.com, fonts.gstatic.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does patron.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 hostname does not respond at all, so anyone typing www.patron.com reaches nothing.
How easily can patron.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 patron.com run?
No analytics or advertising trackers were detected on the homepage of patron.com, which is unusual for a commercial site.
How does patron.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
How are images, fonts and scripts handled?
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 1 external stylesheet and 2 external scripts, with 1 carrying defer or async.
Is patron.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 patron.com?
The homepage carries a noindex directive, so it is asking search engines to keep it out of results entirely.
The canonical points to a different host (https://bidsy.com/patron), which tells search engines the authoritative copy lives elsewhere.
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 patron.com delivered?
The HTML is served with Cache-Control: no-cache.
Frequently asked questions
Does patron.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 patron.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 patron.com built with?
The homepage exposes these fingerprints: X-Powered-By: Express. 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 patron.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 →