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 (24y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ejercito.mil.co
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 43200 s
- Reverse DNS last checked
- 2026-07-30 09:57 UTC
- Forward DNS last checked
- 2026-07-30 09:57 UTC
Forward DNS records for ejercito.mil.co
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 104.26.12.222 | — | 172326s |
| A | 104.26.13.222 | — | 172326s |
| A | 172.67.71.247 | — | 172326s |
| AAAA | 2606:4700:20::681a:cde | — | 172326s |
| AAAA | 2606:4700:20::681a:dde | — | 172326s |
| AAAA | 2606:4700:20::ac43:47f7 | — | 172326s |
| MX | mx.zoho.com | 10 | — |
| MX | mx2.zoho.com | 20 | — |
| MX | mx3.zoho.com | 50 | — |
| NS | tegan.ns.cloudflare.com | — | — |
| NS | tom.ns.cloudflare.com | — | — |
| TXT | 4dq9p1vztpsw9ktfph1b2fvqz8svf16c | — | — |
| TXT | _globalsign-domain-verification=62-gjlUeVHvHvC47PeoKm3bmWMiqRadyauSjff-bs1 | — | — |
| TXT | dtm-domain-verification=Eu-uB50I9HPmEv-OJ-3SmNLqRsEJYl09HNyH1-7lMxM | — | — |
| TXT | dtm-domain-verification=vz8f2T0NliaS-iyVEbeu0mkW6CQqgDxgxBu64gbLhSE | — | — |
| TXT | google-site-verification=dPIe_nn3I2omZDKiOON-kXDU_u_z1ecCSFiIL6o0haM | — | — |
| TXT | google-site-verification=jGxcjLj1cmeZbqF9QvVRNLqshLoBEa3FvqhNzwpklqE | — | — |
| TXT | um0c1svejqqi7g13rchntpc8qs | — | — |
| TXT | v=DMARC1; p=quarantine; rua=mailto:soportedmarc@ejercito.mil.co; ruf=mailto:soportedmarc@ejercito.mil.co; sp=quarantine | — | — |
| TXT | v=spf1 include:zcsend.net include:_spf.mailersend.net mx a ip4:186.144.33.203 ip4:186.144.33.213 include:zohomail.com exists:%{i}.spf.hc6409-86.iphmx.com include:spf.sealmail.co ~all | — | — |
| TXT | zoho-verification=zb10246443.zmverify.zoho.com | — | — |
| CAA | issue comodoca.com | 0 | — |
| CAA | issue digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issue letsencrypt.org | 0 | — |
| CAA | issue pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issue ssl.com | 0 | — |
| CAA | issuewild comodoca.com | 0 | — |
| CAA | issuewild digicert.com; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild letsencrypt.org | 0 | — |
| CAA | issuewild pki.goog; cansignhttpexchanges=yes | 0 | — |
| CAA | issuewild ssl.com | 0 | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 200.69.104.241
- CIDR range
- 200.69.104.0/22
- IP range (int)
- 3,359,991,808 — 3,359,992,831
- Prefix length
- /22
- Organization
- Colombia
- ASN
- AS19429
- ASN name
- Colombia
- Location
- Zipaquirá, Cundinamarca, Colombia
- Coordinates
- 5.018400, -74.007900
- Accuracy radius
- 20 km
- Postal code
- 250258
- Regional Internet Registry
- LACNIC
- Allocated
- 2002-06-11
- Data source(s)
- maxmind_city, maxmind_asn, maxmind_country, ipinfo_lite
- Last updated
- 2026-06-16 12:23:35
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 200.69.104.241?
200.69.104.241 is allocated to Colombia (AS19429), registered in Zipaquirá, Colombia.
Where is 200.69.104.241 located?
The geolocation for 200.69.104.241 maps to Zipaquirá, Colombia 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 200.69.104.241 on?
200.69.104.241 belongs to the 200.69.104.0/22 network block announced by AS19429. This range contains 1,024 addresses.
Does 200.69.104.241 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.
