City: Bogotá
Region: Bogota D.C.
Country: Colombia
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b'% IP Client: 8.214.16.196
% Joint Whois - whois.lacnic.net
% This server accepts single ASN, IPv4 or IPv6 queries
% LACNIC resource: whois.lacnic.net
% Copyright LACNIC lacnic.net
% The data below is provided for information purposes
% and to assist persons in obtaining information about or
% related to AS and IP numbers registrations
% By submitting a whois query, you agree to use this data
% only for lawful purposes.
% 2026-07-27 05:10:58 (-03 -03:00)
inetnum: 2803:9810:6800::/40
status: reallocated
aut-num: N/A
owner: Starlink Colombia S.A.S.
ownerid: CO-SCSA87-LACNIC
responsible: Luis Anzola
address: Calle 97 A No.8-10, 202,
address: - Bogota -
country: CO
phone: +1 3103636000
owner-c: SKH4
tech-c: SKH4
abuse-c: SKH4
created: 20251103
changed: 20251103
inetnum-up: 2803:9810::/32
nic-hdl: SKH4
person: Reyan Pina
e-mail: starlink-admin@spacex.com
address: 1 Rocket Rd, 1, -
address: 90250 - Hawthorne - CA
country: US
phone: +1 3103636000 [0000]
created: 20200813
changed: 20260213
% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.'b'
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> 2803:9810:6877:910:1cb8:455e:923b:8866
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 59191
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;2803:9810:6877:910:1cb8:455e:923b:8866. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Jul 27 16:16:23 CST 2026
;; MSG SIZE rcvd: 67
'6.6.8.8.b.3.2.9.e.5.5.4.8.b.c.1.0.1.9.0.7.7.8.6.0.1.8.9.3.0.8.2.ip6.arpa domain name pointer customer.bgtacol1.isp.starlink.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
6.6.8.8.b.3.2.9.e.5.5.4.8.b.c.1.0.1.9.0.7.7.8.6.0.1.8.9.3.0.8.2.ip6.arpa name = customer.bgtacol1.isp.starlink.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 49.207.200.230 | attackspam | Attempts against non-existent wp-login |
2020-09-06 06:15:36 |
| 64.227.0.131 | attackbotsspam | Sep 6 00:27:37 tor-proxy-02 sshd\[28827\]: User root from 64.227.0.131 not allowed because not listed in AllowUsers Sep 6 00:27:48 tor-proxy-02 sshd\[28829\]: Invalid user oracle from 64.227.0.131 port 45424 Sep 6 00:27:58 tor-proxy-02 sshd\[28831\]: User root from 64.227.0.131 not allowed because not listed in AllowUsers ... |
2020-09-06 06:40:20 |
| 71.73.105.82 | attackbotsspam | Sep 5 19:49:42 ift sshd\[57904\]: Failed password for invalid user admin from 71.73.105.82 port 40888 ssh2Sep 5 19:49:46 ift sshd\[57917\]: Failed password for invalid user admin from 71.73.105.82 port 41052 ssh2Sep 5 19:49:49 ift sshd\[57944\]: Failed password for invalid user admin from 71.73.105.82 port 41133 ssh2Sep 5 19:49:53 ift sshd\[57946\]: Failed password for invalid user admin from 71.73.105.82 port 41215 ssh2Sep 5 19:49:57 ift sshd\[57948\]: Failed password for invalid user admin from 71.73.105.82 port 41317 ssh2 ... |
2020-09-06 06:43:31 |
| 213.141.131.22 | attack | Sep 5 15:01:41 ws24vmsma01 sshd[79280]: Failed password for root from 213.141.131.22 port 53024 ssh2 ... |
2020-09-06 06:28:41 |
| 74.120.14.25 | attackbotsspam |
|
2020-09-06 06:41:54 |
| 185.220.101.9 | attackspambots | $lgm |
2020-09-06 06:30:31 |
| 192.3.204.194 | attack | scanning for potential vulnerable apps (wordpress etc.) and database accesses. Requested URI: /wp/wp-admin/ |
2020-09-06 06:31:41 |
| 66.230.230.230 | attack | Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-09-06 06:39:47 |
| 81.213.219.171 | attack | Automatic report - Port Scan Attack |
2020-09-06 06:24:34 |
| 218.92.0.207 | attackspam | Sep 6 00:23:16 eventyay sshd[691]: Failed password for root from 218.92.0.207 port 51024 ssh2 Sep 6 00:23:19 eventyay sshd[691]: Failed password for root from 218.92.0.207 port 51024 ssh2 Sep 6 00:23:21 eventyay sshd[691]: Failed password for root from 218.92.0.207 port 51024 ssh2 ... |
2020-09-06 06:35:56 |
| 67.205.135.65 | attackbotsspam | Sep 6 02:54:32 gw1 sshd[28114]: Failed password for root from 67.205.135.65 port 46688 ssh2 ... |
2020-09-06 06:17:46 |
| 88.214.57.94 | attackspambots | Port scan on 16 port(s): 4449 5061 5062 5070 5071 5072 5080 5090 5782 6000 6060 7171 8081 8088 8089 9000 |
2020-09-06 06:35:20 |
| 23.160.208.245 | attackbots | Sep 5 22:18:06 eventyay sshd[25290]: Failed password for root from 23.160.208.245 port 42551 ssh2 Sep 5 22:18:08 eventyay sshd[25290]: Failed password for root from 23.160.208.245 port 42551 ssh2 Sep 5 22:18:11 eventyay sshd[25290]: Failed password for root from 23.160.208.245 port 42551 ssh2 Sep 5 22:18:19 eventyay sshd[25290]: Failed password for root from 23.160.208.245 port 42551 ssh2 Sep 5 22:18:19 eventyay sshd[25290]: error: maximum authentication attempts exceeded for root from 23.160.208.245 port 42551 ssh2 [preauth] ... |
2020-09-06 06:38:46 |
| 192.241.230.44 | attackspam | 8983/tcp 9042/tcp 2000/tcp... [2020-08-26/09-05]10pkt,9pt.(tcp) |
2020-09-06 06:29:42 |
| 151.32.45.187 | attack | Aug 30 22:34:35 ingram sshd[1845]: Failed password for r.r from 151.32.45.187 port 48582 ssh2 Aug 30 22:34:41 ingram sshd[1848]: Failed password for r.r from 151.32.45.187 port 48601 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=151.32.45.187 |
2020-09-06 06:25:24 |