digitalsantal.com blocks automated analysis, answering with HTTP 429 to an automated client 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 HTTP 429 to an automated client 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 digitalsantal.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 29% of them (median 496ms) |
|---|---|
| Domain age | Older than 28% of them |
Related domains in this index
Analysed domains sharing the same network (AS15169 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:
When was digitalsantal.com registered?
digitalsantal.com was registered on 2 October 2021, which makes it about 5 years old.
The registrar of record is HOSTINGER operations, UAB.
Registration runs until 2 October 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 2 October 2021 |
|---|---|
| Expires | 2 October 2027 |
| Registrar | HOSTINGER operations, UAB |
| Registry status | client transfer prohibited |
Where is digitalsantal.com hosted?
The first address resolves to infrastructure in Mountain View, United States.
The network is operated by Google LLC (AS15169 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 digitalsantal.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of digitalsantal.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 429 over
HTTPS.
At 861ms to first byte this response is slow for a homepage measured from a single European location.
At 3KB the HTML is unusually small, which typically means the page builds itself client-side after load.
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 | scaffolding on HTTPServer2 |
|---|---|
| Compression | none |
| Page size | 3,194 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 digitalsantal.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-27, which is 83 days from the date of this check. It covers
1 hostname.
- digitalsantal.com
The certificate has 83 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
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 digitalsantal.com?
| IP addresses | 216.239.38.21, 216.239.32.21, 216.239.34.21, 216.239.36.21 |
|---|---|
| Reverse DNS | any-in-2615.1e100.net, any-in-2015.1e100.net |
| Name servers | ns1.dns-parking.com, ns2.dns-parking.com |
| Mail (MX) | no mail records |
| SPF | not published |
| TXT records | 0 |
digitalsantal.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
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 any-in-2615.1e100.net, any-in-2015.1e100.net, which usually names the hosting provider.
Can digitalsantal.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 129 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.digitalsantal.com/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.
Frequently asked questions
Does digitalsantal.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
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 digitalsantal.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 →