texto.com — domain analysis
texto.com is a live website built on WordPress, registered in 1996, served from The Dalles, United States. It has a valid HTTPS certificate, 1 of 6 common security…
texto.com is a live website built on WordPress, registered in 1996, served from The Dalles, United States. It has a valid HTTPS certificate, 1 of 6 common security headers, 1 tracking script.
What is texto.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:
- collateral ×7
- texto ×3
- design ×3
- presentations ×3
- technical ×3
- infographics ×3
- marketing ×3
- graphic ×2
- communication ×2
- home ×2
Does texto.com publish the usual trust pages?
Found: about, contact. Not found at the usual addresses:
privacy, terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does texto.com compare with other domains analysed here?
Measured against the 69 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 22% of them (median 408ms) |
|---|---|
| Security headers | More than 42% of them |
| Domain age | Older than 84% 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.
Analysed domains built on a similar stack:
- adoziox.com
- anthiago.com
- babylist.com
- bahis.com
- bajaj.com
- beerandmagic.com
- bigstata.com
- clearskinstudy.com
Other analysed domains served from the same country:
When was texto.com registered?
texto.com was registered on 3 July 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 Domain.com – Network Solutions, LLC.
Registration runs until 2 July 2030.
| Registered | 3 July 1996 |
|---|---|
| Expires | 2 July 2030 |
| Registrar | Domain.com – Network Solutions, LLC |
| Registry status | active |
Where is texto.com hosted?
The first address resolves to infrastructure in The Dalles, United States.
The network is operated by Google Cloud (us-west1) (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 texto.com running on?
texto.com exposes 4 identifiable technologies: WordPress, jQuery, Google Analytics, X-Powered-By: WP Engine.
WordPress is identifiable from its asset paths, so the platform is public knowledge regardless of whether the version is hidden. That matters mainly for patching discipline: known-platform sites are scanned automatically and constantly.
Visitor tracking is present (Google Analytics), so this homepage is not cookie-free.
- WordPress
- jQuery
- Google Analytics
- X-Powered-By: WP Engine
The page declares a generator of create 2.0.
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 867ms to first byte this response is slow for a homepage measured from a single European location.
The HTML weighs 68KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | nginx |
|---|---|
| Compression | gzip |
| Page size | 69,692 bytes |
| Declared language | en-US |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 40 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 2 H1 headings. One is conventional; several dilute the signal about what the page is primarily about.
All 9 images on the homepage have alt attributes.
| Title | Texto | Graphic Design and Communication (40 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (2 on the page) |
| Canonical | https://texto.com/ |
| Open Graph title | not set |
| Headings / images | 0 H2s, 9 images (0 without alt text) |
Is texto.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-10-31, which is 26 days from the date of this check. It covers
1 hostname.
- texto.com
The certificate has 26 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?
1 of 6 are set (Content Security Policy). Absent: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | yes | upgrade-insecure-requests |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for texto.com?
| IP addresses | 35.233.206.48 |
|---|---|
| Reverse DNS | 48.206.233.35.bc.googleusercontent.com |
| Name servers | ns2.accountsupport.com, ns1.accountsupport.com |
| Mail (MX) | mx2.privateemail.com (pri 10), mx1.privateemail.com (pri 10) |
| SPF | v=spf1 include:spf.privateemail.com ~all |
| TXT records | 2 |
texto.com resolves to a single address, so there is no DNS-level redundancy.
Mail is handled by 2 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 48.206.233.35.bc.googleusercontent.com, which usually names the hosting provider.
Who runs DNS and mail for texto.com?
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
No AAAA records are published, so the site is reachable over IPv4 only.
What else is worth noting about texto.com?
21 of 21 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.
The server discloses software detail in x-powered-by, which tells an attacker what to target without them having to probe for it.
Can texto.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 125 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://texto.com/wp-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.
What does texto.com load from third parties?
The homepage pulls resources from 8 third-party hosts (c0.wp.com, fonts.googleapis.com, gmpg.org, html5shiv.googlecode.com, i0.wp.com, maxcdn.bootstrapcdn.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
The page links or refers to LinkedIn, Facebook, Instagram.
Does texto.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 address redirects to https://texto.com/, so the site settles on one canonical hostname.
How easily can texto.com be crawled?
A sitemap index is served at https://texto.com/wp-sitemap.xml listing 3 entries.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does texto.com run?
1 tracking script detected: Google Analytics.
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 texto.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?
9 images on the homepage, 5 of them lazy-loaded (56%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 30 external stylesheets and 21 external scripts, with 1 carrying defer or async.
Responses carry edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is texto.com accessible and current?
The page uses 4 landmark elements and 8 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index texto.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 37 internal and 9 external links across 3 outside hosts.
Visible text is only 1.5% of the HTML, which indicates the page is assembled in the browser rather than served as content.
The heading outline skips 1 level, which breaks the document structure screen readers navigate by.
How is texto.com delivered?
The HTML is served with Cache-Control: max-age=600, must-revalidate.
Frequently asked questions
Does texto.com set the usual HTTP security headers?
It sets 1 of 6. The ones not present are: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does texto.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 texto.com built with?
The homepage exposes these fingerprints: WordPress, jQuery, Google Analytics, X-Powered-By: WP Engine. 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 texto.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 →
How we estimate this
Every figure on this page is compiled from the public sources cited above and given as a low–typical–high range rather than a single false-precise number. Where costs vary by location we scale the national typical using published state price levels. We recheck figures on a set schedule and stamp each report with the date last verified. We are independent and are never paid to change a number — see how we price things.
