telepase.com.ar is a live website, served from Toronto, Canada. It has a valid HTTPS certificate, 6 of 6 common security headers, 3 tracking scripts.
What is telepase.com.ar 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:
- para ×4
- rutas ×3
- telepase ×2
- principales ×2
- dito ×2
- bito ×2
- modo ×2
- mercadopago ×2
- dispositivo ×2
- cada ×2
Does telepase.com.ar 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 telepase.com.ar compare with other domains analysed here?
Measured against the 75 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 36% of them (median 494ms) |
|---|---|
| Security headers | More than 93% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
Where is telepase.com.ar hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, 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 telepase.com.ar running on?
telepase.com.ar exposes 6 identifiable technologies: Bootstrap, jQuery, Cloudflare, Google Analytics, Google Tag Manager, X-Powered-By: PHP/8.2.34.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
Visitor tracking is present (Google Analytics and Google Tag Manager), so this homepage is not cookie-free.
- Bootstrap
- jQuery
- Cloudflare
- Google Analytics
- Google Tag Manager
- X-Powered-By: PHP/8.2.34
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 692ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 49KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 49,853 bytes |
| Declared language | es |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 24 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.
There are 6 H1 headings. One is conventional; several dilute the signal about what the page is primarily about.
24 of 36 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
| Title | TelePASE – Sitio oficial (24 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | Accedé a las principales rutas y autopistasdel país con un solo click (6 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 11 H2s, 36 images (24 without alt text) |
Is telepase.com.ar served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-05, which is 61 days from the date of this check. It covers
2 hostnames.
- telepase.com.ar
- *.telepase.com.ar
The certificate has 61 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
All 6 headers checked are set, which is uncommon and indicates someone configured them deliberately.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=15552000; preload |
| Content Security Policy | yes | default-src * data: blob: 'unsafe-inline' 'unsafe-eval'; script-src * data: blob: 'unsafe-inline' 'unsafe-eval'; style-s |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | yes | camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self) |
How is DNS configured for telepase.com.ar?
| IP addresses | 104.26.10.116, 104.26.11.116, 172.67.69.143, 2606:4700:20::681a:a74, 2606:4700:20::ac43:458f, 2606:4700:20::681a:b74 |
|---|---|
| Reverse DNS | 104.26.10.116, 104.26.11.116 |
| Name servers | irena.ns.cloudflare.com, kayden.ns.cloudflare.com |
| Mail (MX) | alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), 6bjp34gxdp63vn72ial5m7wzdjog3uetpp5xnqddohd6v5kmknya.mx-verification.google.com (pri 15) |
| SPF | v=spf1 mx a:ASPMX.L.GOOGLE.COM a:ALT1.ASPMX.L.GOOGLE.COM a:ALT2.ASPMX.L.GOOGLE.COM a:ALT3.ASPMX.L.GOOGLE.COM a:ALT4.ASPMX.L.GOOGLE.COM include:spf.mandrillapp.com ~all v=spf1 include:spf.sendinblue.com mx ~all |
| TXT records | 6 |
telepase.com.ar resolves to 6 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 6 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 104.26.10.116, 104.26.11.116, which usually names the hosting provider.
Who runs DNS and mail for telepase.com.ar?
DNS is operated by Cloudflare rather than self-hosted name servers.
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about telepase.com.ar?
6 of 9 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
4 email addresses appear in the homepage markup, where address-harvesting crawlers will find them.
The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.
Can telepase.com.ar be spoofed in email?
DMARC is published with p=none, which monitors but does not act. Forged mail is still delivered; the owner just gets reports about it.
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 24 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 telepase.com.ar load from third parties?
The homepage pulls resources from 10 third-party hosts (ajax.googleapis.com, cdn.jsdelivr.net, cdnjs.cloudflare.com, code.jquery.com, d45mmfengfo52uwkbepmzpzj.agents.do-ai.run, fonts.googleapis.com). Each one sees the visitor IP and user agent on every page load.
2 cookies are set before any interaction (XSRF-TOKEN, telepase_session). 2 lack the Secure flag.
The page links or refers to Facebook, Instagram, YouTube, GitHub.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| XSRF-TOKEN | no | no | lax |
| telepase_session | no | yes | lax |
Does telepase.com.ar settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both telepase.com.ar and www.telepase.com.ar answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can telepase.com.ar 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 telepase.com.ar run?
3 tracking scripts detected: Google Analytics, Google Tag Manager, Meta Pixel.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does telepase.com.ar 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?
36 images on the homepage, 0 of them lazy-loaded (0%).
Modern image formats are in use (3 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 7 external stylesheets and 9 external scripts, with 2 carrying defer or async.
No preconnect hints are declared despite third-party scripts being present, so each new origin pays a full connection setup before it can deliver anything.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is telepase.com.ar accessible and current?
The page uses 7 landmark elements and 11 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index telepase.com.ar?
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.
The homepage carries 43 internal and 25 external links across 14 outside hosts.
Visible text is only 3.4% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is telepase.com.ar delivered?
The HTML is served with Cache-Control: no-cache, private.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
A web app manifest is declared, so the site is installable as a progressive web app.
Frequently asked questions
Does telepase.com.ar set the usual HTTP security headers?
Yes — all 6 headers checked are present.
Does telepase.com.ar allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is telepase.com.ar built with?
The homepage exposes these fingerprints: Bootstrap, jQuery, Cloudflare, Google Analytics, Google Tag Manager, X-Powered-By: PHP/8.2.34. 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 telepase.com.ar 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 →
