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: Kabul

Region: Kabul

Country: Afghanistan

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:
IP Type Details Datetime
103.42.162.30 attackbots
Sep  1 13:27:22 shivevps sshd[27916]: Bad protocol version identification '\024' from 103.42.162.30 port 50060
...
2020-09-02 03:57:47
103.42.124.205 attackspam
Honeypot attack, port: 81, PTR: PTR record not found
2020-06-22 01:05:47
103.42.172.167 attackspambots
firewall-block, port(s): 445/tcp
2020-05-04 00:46:12
103.42.172.167 attackspam
Unauthorized connection attempt from IP address 103.42.172.167 on Port 445(SMB)
2020-04-24 22:14:10
103.42.115.118 attack
Wed, 25 Mar 2020 02:48:26 -0400 Received: from traffic-manage.photon-5.eth01.trafficpollutioncontrol.online ([103.42.115.118]:2625) From: "Tech Smart Card"  India Multi-function Universal Smart Adapter Card box spam
2020-03-26 14:36:58
103.42.158.73 attack
Mar  1 14:16:53 debian-2gb-nbg1-2 kernel: \[5327800.230257\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=103.42.158.73 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x20 TTL=44 ID=42309 PROTO=TCP SPT=52104 DPT=23 WINDOW=53392 RES=0x00 SYN URGP=0
2020-03-02 05:07:17
103.42.172.167 attack
20/2/21@23:45:21: FAIL: Alarm-Intrusion address from=103.42.172.167
...
2020-02-22 19:11:22
103.42.16.254 attack
Host Scan
2019-12-26 17:28:24
103.42.173.80 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 19-12-2019 15:05:15.
2019-12-20 02:36:48
103.42.127.35 attackspam
1576252666 - 12/13/2019 16:57:46 Host: 103.42.127.35/103.42.127.35 Port: 445 TCP Blocked
2019-12-14 01:44:07
103.42.127.223 attackbots
2019-12-04T07:28:34.5313711240 sshd\[29848\]: Invalid user avanthi from 103.42.127.223 port 61951
2019-12-04T07:28:40.5487051240 sshd\[29848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.42.127.223
2019-12-04T07:28:42.2632631240 sshd\[29848\]: Failed password for invalid user avanthi from 103.42.127.223 port 61951 ssh2
...
2019-12-04 16:39:18
103.42.126.254 attack
Automatic report - Banned IP Access
2019-10-25 21:31:40
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.42.1.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38868
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;103.42.1.121.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 13:54:47 CST 2022
;; MSG SIZE  rcvd: 105
Host info
121.1.42.103.in-addr.arpa domain name pointer 103-42-1-121-awcc-mobility-customer.as38742.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
121.1.42.103.in-addr.arpa	name = 103-42-1-121-awcc-mobility-customer.as38742.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
49.235.144.143 attack
Invalid user indra from 49.235.144.143 port 55012
2020-05-13 19:36:15
187.141.128.42 attackbots
2020-05-13T11:04:23.108548abusebot-6.cloudsearch.cf sshd[18796]: Invalid user dedicated from 187.141.128.42 port 54588
2020-05-13T11:04:23.119878abusebot-6.cloudsearch.cf sshd[18796]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.128.42
2020-05-13T11:04:23.108548abusebot-6.cloudsearch.cf sshd[18796]: Invalid user dedicated from 187.141.128.42 port 54588
2020-05-13T11:04:25.546530abusebot-6.cloudsearch.cf sshd[18796]: Failed password for invalid user dedicated from 187.141.128.42 port 54588 ssh2
2020-05-13T11:08:02.696165abusebot-6.cloudsearch.cf sshd[18976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.128.42  user=root
2020-05-13T11:08:04.522848abusebot-6.cloudsearch.cf sshd[18976]: Failed password for root from 187.141.128.42 port 60800 ssh2
2020-05-13T11:11:47.005799abusebot-6.cloudsearch.cf sshd[19160]: Invalid user admin from 187.141.128.42 port 38784
...
2020-05-13 19:55:49
195.54.167.46 attackbotsspam
May 13 13:32:12 debian-2gb-nbg1-2 kernel: \[11628390.919653\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=195.54.167.46 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=28445 PROTO=TCP SPT=51528 DPT=2796 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-13 19:47:10
128.1.91.204 attack
May 13 05:49:29 debian-2gb-nbg1-2 kernel: \[11600629.337289\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=128.1.91.204 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=52708 PROTO=TCP SPT=37438 DPT=8443 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-13 20:01:48
101.162.68.248 attack
might be hacker
2020-05-13 19:21:10
92.63.194.238 attackspambots
Connection by 92.63.194.238 on port: 3390 got caught by honeypot at 5/13/2020 12:15:40 PM
2020-05-13 19:29:47
157.230.127.240 attack
May 13 13:14:54 vpn01 sshd[24978]: Failed password for root from 157.230.127.240 port 49854 ssh2
...
2020-05-13 19:52:55
51.38.230.59 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-05-13 19:23:20
122.51.101.136 attack
May 13 08:32:25 ovpn sshd\[24162\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.101.136  user=backup
May 13 08:32:27 ovpn sshd\[24162\]: Failed password for backup from 122.51.101.136 port 55238 ssh2
May 13 08:51:27 ovpn sshd\[28751\]: Invalid user moreau from 122.51.101.136
May 13 08:51:27 ovpn sshd\[28751\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.101.136
May 13 08:51:29 ovpn sshd\[28751\]: Failed password for invalid user moreau from 122.51.101.136 port 36920 ssh2
2020-05-13 19:51:06
106.13.78.137 attackspambots
May 13 08:56:35 pkdns2 sshd\[62046\]: Invalid user admin from 106.13.78.137May 13 08:56:37 pkdns2 sshd\[62046\]: Failed password for invalid user admin from 106.13.78.137 port 26952 ssh2May 13 09:00:55 pkdns2 sshd\[62261\]: Invalid user wps from 106.13.78.137May 13 09:00:57 pkdns2 sshd\[62261\]: Failed password for invalid user wps from 106.13.78.137 port 18401 ssh2May 13 09:05:13 pkdns2 sshd\[62578\]: Invalid user admin from 106.13.78.137May 13 09:05:16 pkdns2 sshd\[62578\]: Failed password for invalid user admin from 106.13.78.137 port 9856 ssh2
...
2020-05-13 19:24:16
183.89.211.13 attackspambots
Dovecot Invalid User Login Attempt.
2020-05-13 19:53:55
101.162.68.248 attack
might be hacker
2020-05-13 19:21:06
64.225.19.225 attackbotsspam
May 13 10:48:55 l02a sshd[14357]: Invalid user hadoop from 64.225.19.225
May 13 10:48:55 l02a sshd[14357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.19.225 
May 13 10:48:55 l02a sshd[14357]: Invalid user hadoop from 64.225.19.225
May 13 10:48:57 l02a sshd[14357]: Failed password for invalid user hadoop from 64.225.19.225 port 37850 ssh2
2020-05-13 19:30:13
218.92.0.210 attack
May 13 05:43:52 ny01 sshd[7213]: Failed password for root from 218.92.0.210 port 60402 ssh2
May 13 05:50:17 ny01 sshd[7979]: Failed password for root from 218.92.0.210 port 33883 ssh2
May 13 05:50:19 ny01 sshd[7979]: Failed password for root from 218.92.0.210 port 33883 ssh2
2020-05-13 20:01:08
46.105.244.17 attackbotsspam
DATE:2020-05-13 06:49:08, IP:46.105.244.17, PORT:ssh SSH brute force auth (docker-dc)
2020-05-13 19:49:40

Recently Reported IPs

103.41.65.187 103.42.111.109 103.42.111.119 103.42.111.126
103.42.159.0 103.42.180.224 103.42.182.46 103.42.196.196
103.42.225.39 103.42.56.8 103.43.118.76 218.103.137.33
103.43.172.50 103.43.190.195 103.43.44.235 136.31.138.201
103.43.71.230 103.43.79.193 103.44.1.228 103.44.119.250