63.135.180.253
Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Long-established allocation (19y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Isp allocation +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- captive.trilight.net
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 300 s
- Reverse DNS last checked
- 2026-11-12 11:05 UTC
Forward DNS records for captive.trilight.net
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 63.135.180.253 | — | 300s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-11-12 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
- captive.trilight.net — Nov 9, 2026 → present
- host-63-135-180-253.twlakes.net — Nov 8, 2026 → Nov 9, 2026
- captive.trilight.net — Oct 30, 2026 → Nov 8, 2026
- no PTR — Oct 29, 2026 → Oct 30, 2026
- captive.trilight.net — Oct 22, 2026 → Oct 29, 2026
- host-63-135-180-253.twlakes.net — Oct 20, 2026 → Oct 22, 2026
- captive.trilight.net — Oct 17, 2026 → Oct 20, 2026
- host-63-135-180-253.twlakes.net — Oct 16, 2026 → Oct 17, 2026
- captive.trilight.net — Sep 30, 2026 → Oct 16, 2026
- host-63-135-180-253.twlakes.net — Sep 29, 2026 → Sep 30, 2026
- captive.trilight.net — Sep 26, 2026 → Sep 29, 2026
- host-63-135-180-253.twlakes.net — Sep 24, 2026 → Sep 26, 2026
- captive.trilight.net — Aug 23, 2026 → Sep 24, 2026
- host-63-135-180-253.twlakes.net — Jul 8, 2026 → Aug 23, 2026
- captive.trilight.net — Jul 4, 2026 → Jul 8, 2026
- host-63-135-180-253.twlakes.net — Jun 30, 2026 → Jul 4, 2026
- captive.trilight.net — Jun 30, 2026 → Jun 30, 2026
- host-63-135-180-253.twlakes.net — Jun 25, 2026 → Jun 30, 2026
- captive.trilight.net — Jun 22, 2026 → Jun 25, 2026
- host-63-135-180-253.twlakes.net — Jun 19, 2026 → Jun 22, 2026
- captive.trilight.net — Jun 16, 2026 → Jun 19, 2026
- host-63-135-180-253.twlakes.net — Jun 11, 2026 → Jun 16, 2026
Network Allocation for 63.135.180.253
- CIDR range
- 63.135.176.0/21
- IP range (int)
- 1,065,857,024 — 1,065,859,071
- Prefix length
- /21
- Organization
- Twin Lakes Telephone Cooperative Corporation
- ASN
- AS19331
- ASN name
- Twin Lakes Telephone Cooperative Corporation
- Location
- Cookeville, Tennessee, United States
- Coordinates
- 36.217800, -85.542300
- Accuracy radius
- 50 km
- Postal code
- 38501
- Regional Internet Registry
- ARIN
- Allocated
- 2007-08-08
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-11-12 08:43:32
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 63.135.180.253?
63.135.180.253 is allocated to Twin Lakes Telephone Cooperative Corporation (AS19331), registered in Cookeville, United States.
Where is 63.135.180.253 located?
The geolocation for 63.135.180.253 maps to Cookeville, United States based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 63.135.180.253 on?
63.135.180.253 belongs to the 63.135.176.0/21 network block announced by AS19331. This range contains 2,048 addresses.
Does 63.135.180.253 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
