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

Internet Service Provider: TDC

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 <<>> 144.179.27.149
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20601
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 51 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 09 04:31:45 CST 2020
;; MSG SIZE  rcvd: 118
Host info
Host 149.27.179.144.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 149.27.179.144.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
134.209.98.186 attackbotsspam
Jul 17 19:10:30 XXXXXX sshd[14377]: Invalid user dali from 134.209.98.186 port 43754
2019-07-18 04:03:16
46.105.227.206 attackspam
Jul 17 19:32:03 mail sshd\[20876\]: Invalid user admin from 46.105.227.206 port 39342
Jul 17 19:32:03 mail sshd\[20876\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.227.206
Jul 17 19:32:06 mail sshd\[20876\]: Failed password for invalid user admin from 46.105.227.206 port 39342 ssh2
Jul 17 19:36:44 mail sshd\[20934\]: Invalid user sshusr from 46.105.227.206 port 38206
Jul 17 19:36:44 mail sshd\[20934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.227.206
...
2019-07-18 03:53:52
14.36.118.74 attack
Jul 17 18:33:35 bouncer sshd\[19713\]: Invalid user caja from 14.36.118.74 port 49139
Jul 17 18:33:35 bouncer sshd\[19713\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.36.118.74 
Jul 17 18:33:37 bouncer sshd\[19713\]: Failed password for invalid user caja from 14.36.118.74 port 49139 ssh2
...
2019-07-18 03:52:27
190.75.106.163 attack
Unauthorised access (Jul 17) SRC=190.75.106.163 LEN=52 TTL=115 ID=11408 DF TCP DPT=445 WINDOW=8192 SYN
2019-07-18 03:51:03
141.98.80.61 attackbots
Jul 16 12:45:52 rigel postfix/smtpd[7722]: connect from unknown[141.98.80.61]
Jul 16 12:45:53 rigel postfix/smtpd[7722]: warning: unknown[141.98.80.61]: SASL LOGIN authentication failed: authentication failure
Jul 16 12:45:54 rigel postfix/smtpd[7722]: lost connection after AUTH from unknown[141.98.80.61]
Jul 16 12:45:54 rigel postfix/smtpd[7722]: disconnect from unknown[141.98.80.61]
Jul 16 12:45:54 rigel postfix/smtpd[7722]: connect from unknown[141.98.80.61]
Jul 16 12:45:56 rigel postfix/smtpd[7722]: warning: unknown[141.98.80.61]: SASL LOGIN authentication failed: authentication failure
Jul 16 12:45:56 rigel postfix/smtpd[7722]: lost connection after AUTH from unknown[141.98.80.61]
Jul 16 12:45:56 rigel postfix/smtpd[7722]: disconnect from unknown[141.98.80.61]
Jul 16 12:45:58 rigel postfix/smtpd[7722]: connect from unknown[141.98.80.61]
Jul 16 12:46:00 rigel postfix/smtpd[7722]: warning: unknown[141.98.80.61]: SASL LOGIN authentication failed: authentication failur........
-------------------------------
2019-07-18 04:07:32
51.38.51.200 attack
Jul 17 21:55:17 eventyay sshd[31068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.51.200
Jul 17 21:55:19 eventyay sshd[31068]: Failed password for invalid user princess from 51.38.51.200 port 36986 ssh2
Jul 17 22:01:47 eventyay sshd[409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.51.200
...
2019-07-18 04:17:01
152.250.162.32 attackbots
SPLUNK port scan detected:
Jul 17 12:32:45 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=152.250.162.32 DST=104.248.11.191 LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=55309 PROTO=TCP SPT=7240 DPT=34567 WINDOW=5440 RES=0x00 SYN URGP=0
2019-07-18 04:10:57
183.131.82.99 attack
19/7/17@15:46:25: FAIL: Alarm-SSH address from=183.131.82.99
...
2019-07-18 03:55:19
124.65.152.14 attackbotsspam
Automatic report - Banned IP Access
2019-07-18 04:03:32
34.94.101.105 attack
17.07.2019 18:33:27 - Login Fail on hMailserver 
Detected by ELinOX-hMail-A2F
2019-07-18 03:57:30
217.17.120.247 attackspambots
Caught in portsentry honeypot
2019-07-18 03:41:00
112.85.42.227 attackspambots
Jul 17 14:19:41 aat-srv002 sshd[19264]: Failed password for root from 112.85.42.227 port 54070 ssh2
Jul 17 14:35:03 aat-srv002 sshd[19566]: Failed password for root from 112.85.42.227 port 48379 ssh2
Jul 17 14:35:05 aat-srv002 sshd[19566]: Failed password for root from 112.85.42.227 port 48379 ssh2
Jul 17 14:35:07 aat-srv002 sshd[19566]: Failed password for root from 112.85.42.227 port 48379 ssh2
...
2019-07-18 03:42:04
185.232.67.53 attack
[portscan] tcp/22 [SSH]
[scan/connect: 308 time(s)]
*(RWIN=29200)(07172048)
2019-07-18 03:48:52
222.186.15.110 attack
2019-07-17T19:06:46.594012abusebot.cloudsearch.cf sshd\[24475\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.110  user=root
2019-07-18 03:36:08
175.162.250.110 attack
2019-07-17T19:00:51.157839abusebot-4.cloudsearch.cf sshd\[4518\]: Invalid user ubnt from 175.162.250.110 port 58234
2019-07-18 03:36:34

Recently Reported IPs

121.13.221.156 82.65.9.149 204.98.127.15 178.90.153.90
175.167.98.0 71.6.233.205 69.199.77.199 167.119.251.215
14.226.240.244 190.6.147.110 202.151.20.128 58.20.3.141
166.183.35.243 39.52.5.119 144.24.133.245 112.4.189.97
47.26.101.102 56.224.200.250 111.3.153.71 213.46.209.157