Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: France

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 2.21.134.201
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21531
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;2.21.134.201.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025013101 1800 900 604800 86400

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 03:48:42 CST 2025
;; MSG SIZE  rcvd: 105
Host info
201.134.21.2.in-addr.arpa domain name pointer a2-21-134-201.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
201.134.21.2.in-addr.arpa	name = a2-21-134-201.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.248.65.180 attackspambots
Invalid user abe from 104.248.65.180 port 46558
2020-02-13 14:45:08
122.168.24.116 attackspam
...
2020-02-13 14:22:25
1.179.133.214 attack
Feb 12 20:53:25 mockhub sshd[8989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.133.214
Feb 12 20:53:27 mockhub sshd[8989]: Failed password for invalid user supervisor from 1.179.133.214 port 57417 ssh2
...
2020-02-13 14:49:09
66.158.213.242 attack
Automatic report - Port Scan Attack
2020-02-13 14:18:44
140.143.207.208 attackbotsspam
Automatic report - SSH Brute-Force Attack
2020-02-13 14:19:11
51.83.125.8 attack
Invalid user work from 51.83.125.8 port 59888
2020-02-13 14:14:45
87.222.97.100 attackspambots
Feb 13 08:39:58 server sshd\[31589\]: Invalid user db2fenc1 from 87.222.97.100
Feb 13 08:39:58 server sshd\[31589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=100.97.222.87.dynamic.jazztel.es 
Feb 13 08:40:01 server sshd\[31589\]: Failed password for invalid user db2fenc1 from 87.222.97.100 port 50735 ssh2
Feb 13 08:57:48 server sshd\[2073\]: Invalid user tuan from 87.222.97.100
Feb 13 08:57:48 server sshd\[2073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=100.97.222.87.dynamic.jazztel.es 
...
2020-02-13 14:28:05
181.72.34.201 attack
Feb 13 06:54:04 ncomp sshd[23962]: Invalid user test from 181.72.34.201
Feb 13 06:54:04 ncomp sshd[23962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.72.34.201
Feb 13 06:54:04 ncomp sshd[23962]: Invalid user test from 181.72.34.201
Feb 13 06:54:06 ncomp sshd[23962]: Failed password for invalid user test from 181.72.34.201 port 46615 ssh2
2020-02-13 14:17:20
189.11.172.52 attackspam
Tried sshing with brute force.
2020-02-13 14:34:21
185.176.27.170 attackbotsspam
02/13/2020-06:48:20.884574 185.176.27.170 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-02-13 14:32:04
2.230.149.202 attackbotsspam
02/13/2020-05:54:04.019175 2.230.149.202 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 7
2020-02-13 14:19:55
222.186.175.140 attackspambots
Feb 13 07:29:03 legacy sshd[29159]: Failed password for root from 222.186.175.140 port 40860 ssh2
Feb 13 07:29:16 legacy sshd[29159]: error: maximum authentication attempts exceeded for root from 222.186.175.140 port 40860 ssh2 [preauth]
Feb 13 07:29:22 legacy sshd[29167]: Failed password for root from 222.186.175.140 port 54528 ssh2
...
2020-02-13 14:43:38
119.187.151.218 attack
Feb 13 05:52:48 h2497892 dovecot: pop3-login: Disconnected \(no auth attempts in 0 secs\): user=\<\>, rip=119.187.151.218, lip=85.214.205.138, session=\
Feb 13 05:53:03 h2497892 dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 6 secs\): user=\, method=PLAIN, rip=119.187.151.218, lip=85.214.205.138, session=\<3WDV3G2e8Kl3u5fa\>
Feb 13 05:53:28 h2497892 dovecot: pop3-login: Aborted login \(auth failed, 1 attempts in 6 secs\): user=\, method=PLAIN, rip=119.187.151.218, lip=85.214.205.138, session=\
...
2020-02-13 14:44:42
116.206.40.44 attackbots
[Thu Feb 13 11:54:09.296635 2020] [:error] [pid 29333:tid 140024179844864] [client 116.206.40.44:58479] [client 116.206.40.44] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 500 found within RESPONSE_STATUS: 500"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/images/1.svg"] [unique_id "XkTWZZOePmzR7ExralD6pQAAAU4"], referer: https://karangploso.jatim.bmkg.go.id/
...
2020-02-13 14:15:45
113.168.64.69 attack
1581569645 - 02/13/2020 05:54:05 Host: 113.168.64.69/113.168.64.69 Port: 445 TCP Blocked
2020-02-13 14:18:10

Recently Reported IPs

246.39.100.159 167.145.177.198 248.195.121.37 77.134.84.162
228.146.42.90 200.173.20.154 171.207.117.116 145.17.45.157
248.50.251.159 141.249.21.229 124.68.87.112 5.197.62.219
193.255.2.150 251.230.108.10 116.66.184.230 138.212.254.1
189.46.32.204 236.55.146.209 25.203.134.216 39.25.23.61