174.21.149.122

Basic Info

City: Seattle

Region: Washington

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: CenturyLink Communications, LLC

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

No discussion about this subnet yet..

Whois info:

Dig info:


; <<>> DiG 9.10.3-P4-Ubuntu <<>> 174.21.149.122
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1560
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Sun Mar 31 10:44:16 +08 2019
;; MSG SIZE  rcvd: 118

Host info

122.149.21.174.in-addr.arpa domain name pointer 174-21-149-122.tukw.qwest.net.

Nslookup info:

Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
122.149.21.174.in-addr.arpa	name = 174-21-149-122.tukw.qwest.net.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
194.26.29.114	attackspam	Fail2Ban Ban Triggered	2020-02-09 13:10:31
78.49.132.212	attackbots	Feb 9 01:44:54 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=78.49.132.212, lip=144.91.77.193, session= Feb 9 01:45:01 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 7 secs): user=, method=PLAIN, rip=78.49.132.212, lip=144.91.77.193, session=<8W1g7hmePcVOMYTU> Feb 9 01:45:08 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 7 secs): user=, method=PLAIN, rip=78.49.132.212, lip=144.91.77.193, session= Feb 9 01:45:10 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=78.49.132.212, lip=144.91.77.193, session=<5oVA7xmeP8VOMYTU> Feb 9 01:45:12 server dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=78.49.132.212, lip=144.91.77.193, session=<6l9c7xmeQMVOMYTU>	2020-02-09 11:03:18
95.163.209.254	attack	SSH Bruteforce attack	2020-02-09 13:10:55
111.30.31.176	attackspambots	Brute force attempt	2020-02-09 11:07:02
202.50.52.100	attackspambots	Automatic report - Port Scan	2020-02-09 13:20:05
51.38.236.221	attack	Feb 9 05:55:31 h1745522 sshd[21811]: Invalid user vuw from 51.38.236.221 port 49502 Feb 9 05:55:31 h1745522 sshd[21811]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.236.221 Feb 9 05:55:31 h1745522 sshd[21811]: Invalid user vuw from 51.38.236.221 port 49502 Feb 9 05:55:33 h1745522 sshd[21811]: Failed password for invalid user vuw from 51.38.236.221 port 49502 ssh2 Feb 9 05:56:57 h1745522 sshd[21892]: Invalid user lzb from 51.38.236.221 port 34750 Feb 9 05:56:57 h1745522 sshd[21892]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.236.221 Feb 9 05:56:57 h1745522 sshd[21892]: Invalid user lzb from 51.38.236.221 port 34750 Feb 9 05:57:00 h1745522 sshd[21892]: Failed password for invalid user lzb from 51.38.236.221 port 34750 ssh2 Feb 9 05:58:27 h1745522 sshd[22027]: Invalid user glu from 51.38.236.221 port 48188 ...	2020-02-09 13:34:31
1.171.50.231	attack	port scan and connect, tcp 23 (telnet)	2020-02-09 13:04:16
54.38.160.4	attackbots	Feb 9 00:30:32 plusreed sshd[29743]: Invalid user iww from 54.38.160.4 ...	2020-02-09 13:33:04
74.71.106.196	attackspambots	$f2bV_matches	2020-02-09 13:12:12
139.162.122.110	attackbots	2020-02-09T04:59:01.178185Z 45552ecb8cbc New connection: 139.162.122.110:48924 (172.17.0.5:2222) [session: 45552ecb8cbc] 2020-02-09T04:59:01.651797Z 3c203fdf7ed3 New connection: 139.162.122.110:49200 (172.17.0.5:2222) [session: 3c203fdf7ed3]	2020-02-09 13:12:57
181.57.2.98	attackbots	2020-02-09T04:53:35.333411shield sshd\[26644\]: Invalid user hsj from 181.57.2.98 port 55263 2020-02-09T04:53:35.340102shield sshd\[26644\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.57.2.98 2020-02-09T04:53:36.949710shield sshd\[26644\]: Failed password for invalid user hsj from 181.57.2.98 port 55263 ssh2 2020-02-09T04:58:47.867005shield sshd\[27410\]: Invalid user ln from 181.57.2.98 port 41550 2020-02-09T04:58:47.872700shield sshd\[27410\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.57.2.98	2020-02-09 13:20:26
187.109.221.38	attackspambots	Unauthorized connection attempt from IP address 187.109.221.38 on Port 445(SMB)	2020-02-09 11:04:16
165.22.245.236	attack	Feb 9 05:58:37 cp sshd[32390]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.245.236 Feb 9 05:58:37 cp sshd[32390]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.245.236	2020-02-09 13:26:36
43.255.118.170	attackspambots	Port probing on unauthorized port 1433	2020-02-09 13:38:54
222.186.175.212	attackbotsspam	Feb 9 05:59:04 ns382633 sshd\[6368\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212 user=root Feb 9 05:59:06 ns382633 sshd\[6368\]: Failed password for root from 222.186.175.212 port 29664 ssh2 Feb 9 05:59:10 ns382633 sshd\[6368\]: Failed password for root from 222.186.175.212 port 29664 ssh2 Feb 9 05:59:13 ns382633 sshd\[6368\]: Failed password for root from 222.186.175.212 port 29664 ssh2 Feb 9 05:59:16 ns382633 sshd\[6368\]: Failed password for root from 222.186.175.212 port 29664 ssh2	2020-02-09 13:01:14

Recently Reported IPs

51.38.90.195	211.159.152.252	177.144.136.133	94.102.56.252
82.100.63.189	222.122.202.35	162.252.156.95	114.113.144.104
81.136.241.89	37.99.136.209	47.91.159.88	106.13.9.153
106.12.37.232	154.73.109.10	83.249.124.62	80.211.148.158
51.255.35.41	132.145.40.25	80.151.229.8	206.189.131.213