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

Internet Service Provider: Tata Teleservices Ltd

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
Type Details Datetime
attackspam
2019-11-20 05:50:52 H=(dmz.tieto.com) [49.248.12.226]:18021 I=[10.100.18.21]:25 F=: Host/domain is listed in RBL cbl.abuseat.org (Blocked - see hxxp://www.abuseat.org/lookup.cgi?ip=49.248.12.226)
2019-11-20 05:50:53 unexpected disconnection while reading SMTP command from (dmz.tieto.com) [49.248.12.226]:18021 I=[10.100.18.21]:25 (error: Connection reset by peer)
2019-11-20 07:12:04 H=(dmz.tieto.com) [49.248.12.226]:15823 I=[10.100.18.21]:25 F=: Host/domain is listed in RBL cbl.abuseat.org (Blocked - see hxxp://www.abuseat.org/lookup.cgi?ip=49.248.12.226)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.248.12.226
2019-11-20 17:50:56
Comments on same subnet:
IP Type Details Datetime
49.248.120.75 attack
Unauthorized connection attempt from IP address 49.248.120.75 on Port 445(SMB)
2020-07-14 05:09:28
49.248.121.10 attackbotsspam
2020-05-29T07:54:40.085410abusebot-4.cloudsearch.cf sshd[29114]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.248.121.10  user=root
2020-05-29T07:54:42.936008abusebot-4.cloudsearch.cf sshd[29114]: Failed password for root from 49.248.121.10 port 33384 ssh2
2020-05-29T07:57:34.087026abusebot-4.cloudsearch.cf sshd[29265]: Invalid user frants from 49.248.121.10 port 36544
2020-05-29T07:57:34.097524abusebot-4.cloudsearch.cf sshd[29265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.248.121.10
2020-05-29T07:57:34.087026abusebot-4.cloudsearch.cf sshd[29265]: Invalid user frants from 49.248.121.10 port 36544
2020-05-29T07:57:35.832905abusebot-4.cloudsearch.cf sshd[29265]: Failed password for invalid user frants from 49.248.121.10 port 36544 ssh2
2020-05-29T08:00:18.283323abusebot-4.cloudsearch.cf sshd[29455]: Invalid user leanora from 49.248.121.10 port 39696
...
2020-05-29 18:14:08
49.248.121.10 attack
DATE:2020-05-24 00:07:43, IP:49.248.121.10, PORT:ssh SSH brute force auth (docker-dc)
2020-05-24 06:09:21
49.248.127.175 attack
port scan and connect, tcp 8000 (http-alt)
2020-05-07 20:45:31
49.248.12.82 attackbotsspam
Unauthorized connection attempt from IP address 49.248.12.82 on Port 445(SMB)
2020-05-07 20:26:47
49.248.121.10 attackspam
2020-05-05T22:17:33.858385  sshd[8294]: Invalid user ftpadmin from 49.248.121.10 port 57810
2020-05-05T22:17:33.872052  sshd[8294]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.248.121.10
2020-05-05T22:17:33.858385  sshd[8294]: Invalid user ftpadmin from 49.248.121.10 port 57810
2020-05-05T22:17:36.319292  sshd[8294]: Failed password for invalid user ftpadmin from 49.248.121.10 port 57810 ssh2
...
2020-05-06 05:54:12
49.248.12.82 attack
Unauthorized connection attempt from IP address 49.248.12.82 on Port 445(SMB)
2020-05-05 09:37:27
49.248.120.154 attack
Unauthorized connection attempt from IP address 49.248.120.154 on Port 445(SMB)
2019-12-21 15:20:08
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.248.12.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41977
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;49.248.12.226.			IN	A

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

;; Query time: 785 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Nov 20 17:50:53 CST 2019
;; MSG SIZE  rcvd: 117
Host info
226.12.248.49.in-addr.arpa domain name pointer dmz.tieto.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
226.12.248.49.in-addr.arpa	name = dmz.tieto.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
51.254.164.230 attackspam
Jun 30 11:36:26 SilenceServices sshd[17400]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.164.230
Jun 30 11:36:28 SilenceServices sshd[17400]: Failed password for invalid user anouk from 51.254.164.230 port 57652 ssh2
Jun 30 11:37:14 SilenceServices sshd[17927]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.164.230
2019-06-30 17:40:55
164.132.197.108 attackbots
$f2bV_matches
2019-06-30 18:16:05
121.208.177.47 attack
Jun 30 08:31:14 localhost sshd\[118448\]: Invalid user pi from 121.208.177.47 port 54466
Jun 30 08:31:14 localhost sshd\[118450\]: Invalid user pi from 121.208.177.47 port 54468
Jun 30 08:31:14 localhost sshd\[118448\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.208.177.47
Jun 30 08:31:14 localhost sshd\[118450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.208.177.47
Jun 30 08:31:16 localhost sshd\[118448\]: Failed password for invalid user pi from 121.208.177.47 port 54466 ssh2
...
2019-06-30 18:12:10
221.122.73.130 attack
Jun 30 05:54:04 vps200512 sshd\[32551\]: Invalid user emiliojose from 221.122.73.130
Jun 30 05:54:04 vps200512 sshd\[32551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.73.130
Jun 30 05:54:06 vps200512 sshd\[32551\]: Failed password for invalid user emiliojose from 221.122.73.130 port 40999 ssh2
Jun 30 05:57:52 vps200512 sshd\[32585\]: Invalid user uftp from 221.122.73.130
Jun 30 05:57:52 vps200512 sshd\[32585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.73.130
2019-06-30 18:18:57
217.132.174.213 attack
Honeypot attack, port: 81, PTR: dsl217-132-174-213.bb.netvision.net.il.
2019-06-30 17:29:57
103.80.117.214 attackspam
$f2bV_matches
2019-06-30 18:31:26
182.61.12.218 attackbots
2019-06-30T11:13:16.883711  sshd[5654]: Invalid user guest from 182.61.12.218 port 45474
2019-06-30T11:13:16.898405  sshd[5654]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.12.218
2019-06-30T11:13:16.883711  sshd[5654]: Invalid user guest from 182.61.12.218 port 45474
2019-06-30T11:13:18.960220  sshd[5654]: Failed password for invalid user guest from 182.61.12.218 port 45474 ssh2
2019-06-30T11:15:31.851516  sshd[5701]: Invalid user zao from 182.61.12.218 port 35924
...
2019-06-30 18:14:56
129.204.58.180 attackspambots
Jun 30 07:28:00 server sshd[20676]: Failed password for invalid user peoplesoft from 129.204.58.180 port 59507 ssh2
Jun 30 07:31:04 server sshd[21332]: Failed password for invalid user oracle from 129.204.58.180 port 45488 ssh2
Jun 30 07:33:03 server sshd[21787]: Failed password for invalid user trombone from 129.204.58.180 port 53997 ssh2
2019-06-30 18:20:13
185.153.196.191 attack
Multiport scan : 14 ports scanned 11141 13908 13950 14004 15188 15219 15568 16217 16836 17922 18018 18242 18434 18978
2019-06-30 18:25:32
35.240.55.191 attackbotsspam
$f2bV_matches
2019-06-30 18:03:19
42.232.218.228 attackbotsspam
Jun 30 03:36:31 *** sshd[23719]: User root from 42.232.218.228 not allowed because not listed in AllowUsers
2019-06-30 17:56:22
82.239.89.166 attackspam
$f2bV_matches
2019-06-30 18:05:05
210.74.148.94 attackspambots
Port Scan 3389
2019-06-30 18:20:50
175.175.253.116 attackspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-06-30 17:48:58
218.92.0.200 attack
SSH Brute-Force reported by Fail2Ban
2019-06-30 18:23:57

Recently Reported IPs

154.189.93.186 182.101.38.47 111.182.110.86 74.91.122.68
182.247.60.182 103.192.76.93 113.100.89.191 139.99.196.73
36.6.135.8 36.237.205.30 123.139.33.69 222.211.163.202
14.112.230.176 106.56.247.148 220.133.141.57 112.194.65.166
112.205.100.9 222.66.38.46 60.172.70.52 113.190.130.87