texautoreply.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 64 days left4 years old
70
texautoreply.net was registered on 17 May 2022 via GoDaddy.com, LLC and the registry expiry is 17 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/texautoreply.net.
texautoreply.net publishes 2 nameservers. DNSSEC is not signed.
texautoreply.net has 1 IPv4 address (173.254.28.25). The geolocation database places 173.254.28.25 in Phoenix, United States.
The TLS certificate from YR2 is valid and has 64 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Contact Form 7, Google Analytics, MySQL, Nginx, PHP, WordPress, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for texautoreply.net in the checks that ran.
Domain · RDAP/WHOIS
texautoreply.net was registered on 17 May 2022 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/texautoreply.net.
| Registered | since 17 May 2022 |
|---|---|
| Created | 17 May 2022 |
| Updated | 18 May 2026 |
| Expires | 17 May 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns1.justhost.com, ns2.justhost.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/texautoreply.net |
texautoreply.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
texautoreply.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
texautoreply.net carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
texautoreply.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns1.justhost.com is published for texautoreply.net in the registration record from https://rdap.verisign.com/net/v1/domain/texautoreply.net.
Nameserver ns2.justhost.com is published for texautoreply.net in the registration record from https://rdap.verisign.com/net/v1/domain/texautoreply.net.
DNS
texautoreply.net has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 173.254.28.25 |
|---|---|
| AAAA | — |
| NS | ns1.justhost.com, ns2.justhost.com |
| MX | mail.texautoreply.net (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at texautoreply.net is "v=spf1 a mx include:websitewelcome.com ~all".
IPv4 address 173.254.28.25 answers for texautoreply.net at resolver 1.1.1.1:53.
Mail exchanger mail.texautoreply.net has preference 0.
Hosting and geo
texautoreply.net is placed in Phoenix, United States by the local geolocation database (db-ip).
| Address | 173.254.28.25 |
|---|---|
| Country | United States |
| City | Phoenix |
| Source | db-ip |
SSL/TLS
The certificate for texautoreply.net is valid, with 64 days left and 23 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | autoconfig.texautoreply.net |
| Valid from | 6 October 2026 |
| Valid until | 4 January 2027 |
| Days left | 64 |
| SAN count | 23 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: autoconfig.texautoreply.net, autoconfig.trasferirefile.com, autodiscover.texautoreply.net, autodiscover.trasferirefile.com, cpanel.texautoreply.net, cpanel.trasferirefile.com, cpcalendars.texautoreply.net, cpcontacts.texautoreply.net, mail.texautoreply.net, mail.trasferirefile.com, mail.tyx.wng.mybluehost.me, texautoreply-net.trasferirefile.com, texautoreply.net, trasferirefile.com, tyx.wng.mybluehost.me, webdisk.texautoreply.net, webdisk.trasferirefile.com, webmail.texautoreply.net, webmail.trasferirefile.com, www.texautoreply-net.trasferirefile.com, www.texautoreply.net, www.trasferirefile.com, www.tyx.wng.mybluehost.me.
Tech stack
Tech detection checked the fetched homepage and named 9 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Contact Form 7 · WordPress plugins, Form builders
- Google Analytics · Analytics
- MySQL · Databases
- Nginx · Web servers, Reverse proxies
- PHP · Programming languages
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
- jQuery Migrate · JavaScript libraries
Bootstrap is filed under UI frameworks.
Contact Form 7 is filed under WordPress plugins, Form builders.
Google Analytics is filed under Analytics.
MySQL is filed under Databases.
Nginx is filed under Web servers, Reverse proxies.
PHP is filed under Programming languages.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
jQuery Migrate is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 1315 ms. The target title is 43 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 1315 ms |
| Title length | 43 yes |
| Quoted title | "TexAutoReply | Telegram Auto Reply Software" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | / |
| Language | en-US |
| Links | 23 |
| Images | 9 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for texautoreply.net is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Phoenix.
- October 2026: geo country changed from empty to United States.
Questions
Is texautoreply.net safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts texautoreply.net?
texautoreply.net is placed in Phoenix, United States.
When does texautoreply.net expire?
texautoreply.net expires on 17 May 2027 according to https://rdap.verisign.com/net/v1/domain/texautoreply.net.
Who owns texautoreply.net?
The registry did not return a person or a company for texautoreply.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/texautoreply.net at 2026-10-30T14:55:58Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:55:58Z
- TLS source tls:443 at 2026-10-30T14:55:58Z
- HTTP source https://texautoreply.net/ at 2026-10-30T14:55:58Z
- Tech source wappalyzergo at 2026-10-30T14:55:58Z
- Geo source db-ip at 2026-10-30T14:55:58Z
- Safety source family DNS and local lists at 2026-10-30T14:55:58Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.