Texas Insurance
https://texasautoquotes.comReturns indicative auto insurance prices to a consumer's agent in exchange for rating facts, and connects the consumer with licensed agents on consent. No contact details required for a price.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 244ms · p95 397msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/3/2026, 4:00:00 AM | 100% | 1 | 140ms |
| 9/3/2026, 5:00:00 AM | 100% | 1 | 136ms |
| 9/3/2026, 6:00:00 AM | 100% | 1 | 149ms |
| 9/3/2026, 7:00:00 AM | 100% | 1 | 295ms |
| 9/3/2026, 8:00:00 AM | 100% | 1 | 241ms |
| 9/3/2026, 9:00:00 AM | 100% | 1 | 245ms |
| 9/3/2026, 11:00:00 AM | 100% | 1 | 243ms |
| 9/3/2026, 12:00:00 PM | 100% | 1 | 130ms |
| 9/3/2026, 1:00:00 PM | 100% | 1 | 244ms |
| 9/3/2026, 2:00:00 PM | 100% | 1 | 306ms |
| 9/3/2026, 3:00:00 PM | 100% | 1 | 142ms |
| 9/3/2026, 4:00:00 PM | 100% | 1 | 129ms |
| 9/3/2026, 6:00:00 PM | 100% | 1 | 308ms |
| 9/3/2026, 7:00:00 PM | 100% | 1 | 471ms |
| 9/3/2026, 8:00:00 PM | 100% | 1 | 251ms |
| 9/3/2026, 9:00:00 PM | 100% | 1 | 129ms |
| 9/3/2026, 10:00:00 PM | 100% | 1 | 128ms |
| 9/3/2026, 11:00:00 PM | 100% | 1 | 337ms |
| 9/4/2026, 1:00:00 AM | 100% | 1 | 112ms |
| 9/4/2026, 2:00:00 AM | 100% | 1 | 252ms |
| 9/4/2026, 3:00:00 AM | 100% | 1 | 250ms |
| 9/4/2026, 4:00:00 AM | 100% | 1 | 134ms |
| 9/4/2026, 5:00:00 AM | 100% | 1 | 244ms |
| 9/4/2026, 6:00:00 AM | 100% | 1 | 139ms |
| 9/4/2026, 8:00:00 AM | 100% | 1 | 129ms |
| 9/4/2026, 9:00:00 AM | 100% | 1 | 138ms |
| 9/4/2026, 10:00:00 AM | 100% | 1 | 117ms |
| 9/4/2026, 11:00:00 AM | 100% | 1 | 101ms |
| 9/4/2026, 12:00:00 PM | 100% | 1 | 253ms |
| 9/4/2026, 1:00:00 PM | 100% | 1 | 107ms |
| 9/4/2026, 3:00:00 PM | 100% | 1 | 138ms |
| 9/4/2026, 4:00:00 PM | 100% | 1 | 193ms |
| 9/4/2026, 5:00:00 PM | 100% | 1 | 286ms |
| 9/4/2026, 6:00:00 PM | 100% | 1 | 290ms |
| 9/4/2026, 7:00:00 PM | 100% | 1 | 133ms |
| 9/4/2026, 8:00:00 PM | 100% | 1 | 266ms |
| 9/4/2026, 10:00:00 PM | 100% | 1 | 283ms |
| 9/4/2026, 11:00:00 PM | 100% | 1 | 131ms |
| 9/5/2026, 12:00:00 AM | 100% | 1 | 125ms |
| 9/5/2026, 1:00:00 AM | 100% | 1 | 277ms |
| 9/5/2026, 2:00:00 AM | 100% | 1 | 323ms |
| 9/5/2026, 3:00:00 AM | 100% | 1 | 290ms |
| 9/5/2026, 5:00:00 AM | 100% | 1 | 124ms |
| 9/5/2026, 6:00:00 AM | 100% | 1 | 123ms |
| 9/5/2026, 7:00:00 AM | 100% | 1 | 415ms |
| 9/5/2026, 8:00:00 AM | 100% | 1 | 97ms |
| 9/5/2026, 9:00:00 AM | 100% | 1 | 298ms |
| 9/5/2026, 10:00:00 AM | 100% | 1 | 106ms |
| 9/5/2026, 11:00:00 AM | 100% | 1 | 107ms |
| 9/5/2026, 1:00:00 PM | 100% | 1 | 316ms |
| 9/5/2026, 2:00:00 PM | 100% | 1 | 370ms |
| 9/5/2026, 3:00:00 PM | 100% | 1 | 330ms |
| 9/5/2026, 4:00:00 PM | 100% | 1 | 420ms |
| 9/5/2026, 5:00:00 PM | 100% | 1 | 149ms |
| 9/5/2026, 6:00:00 PM | 100% | 1 | 124ms |
| 9/5/2026, 7:00:00 PM | 100% | 1 | 137ms |
| 9/5/2026, 9:00:00 PM | 100% | 1 | 131ms |
| 9/5/2026, 10:00:00 PM | 100% | 1 | 364ms |
| 9/5/2026, 11:00:00 PM | 100% | 1 | 127ms |
| 9/6/2026, 12:00:00 AM | 100% | 1 | 305ms |
| 9/6/2026, 1:00:00 AM | 100% | 1 | 310ms |
| 9/6/2026, 2:00:00 AM | 100% | 1 | 130ms |
| 9/6/2026, 4:00:00 AM | 100% | 1 | 118ms |
| 9/6/2026, 5:00:00 AM | 100% | 1 | 166ms |
| 9/6/2026, 6:00:00 AM | 100% | 1 | 127ms |
| 9/6/2026, 7:00:00 AM | 100% | 1 | 420ms |
| 9/6/2026, 8:00:00 AM | 100% | 1 | 320ms |
| 9/6/2026, 9:00:00 AM | 100% | 1 | 128ms |
| 9/6/2026, 11:00:00 AM | 100% | 1 | 325ms |
| 9/6/2026, 12:00:00 PM | 100% | 1 | 331ms |
| 9/6/2026, 1:00:00 PM | 100% | 1 | 350ms |
| 9/6/2026, 2:00:00 PM | 100% | 1 | 365ms |
| 9/6/2026, 4:00:00 PM | 100% | 1 | 297ms |
| 9/6/2026, 6:00:00 PM | 100% | 1 | 306ms |
| 9/6/2026, 8:00:00 PM | 100% | 1 | 135ms |
| 9/6/2026, 10:00:00 PM | 100% | 1 | 375ms |
| 9/7/2026, 12:00:00 AM | 100% | 1 | 394ms |
| 9/7/2026, 2:00:00 AM | 100% | 1 | 346ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 6
- Activity
- not yet measured
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- —
- Networks
- —
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Name.com, Inc.
- Domain registered
- 2026-09-02
- Hosting network
- RS-1125
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.