149.80.56.145 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

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

;; QUESTION SECTION:
;149.80.56.145.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 07 12:00:47 CST 2025
;; MSG SIZE  rcvd: 106

Host info

Host 145.56.80.149.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 145.56.80.149.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
134.249.132.15	attackbots	Automatic report - Port Scan Attack	2020-08-27 22:05:43
189.45.234.58	attackspam	Icarus honeypot on github	2020-08-27 22:04:42
212.129.16.53	attack	IP blocked	2020-08-27 21:25:45
191.53.248.21	attackbots	(smtpauth) Failed SMTP AUTH login from 191.53.248.21 (BR/Brazil/191-53-248-21.nvs-wr.mastercabo.com.br): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-07-28 04:00:36 plain authenticator failed for ([191.53.248.21]) [191.53.248.21]: 535 Incorrect authentication data (set_id=info@negintabas.ir)	2020-08-27 21:40:07
46.83.37.243	attackspambots	Aug 26 14:12:41 minden010 postfix/smtpd[7357]: NOQUEUE: reject: RCPT from p2e5325f3.dip0.t-ipconnect.de[46.83.37.243]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo= Aug 26 14:12:41 minden010 postfix/smtpd[11943]: NOQUEUE: reject: RCPT from p2e5325f3.dip0.t-ipconnect.de[46.83.37.243]: 450 4.7.1 : Helo command rejected: Host not found; from=<> to= proto=ESMTP helo= Aug 26 14:12:41 minden010 postfix/smtpd[7353]: NOQUEUE: reject: RCPT from p2e5325f3.dip0.t-ipconnect.de[46.83.37.243]: 450 4.7.1 : Helo command rejected: Host not found; from=<> to= proto=ESMTP helo= Aug 26 14:16:24 minden010 postfix/smtpd[7357]: NOQUEUE: reject: RCPT from p2e5325f3.dip0.t-ipconnect.de[46.83.37.243]: 450 4.7.1 : Helo command rejected: Host not found; from= to= proto=ESMTP helo=	2020-08-27 21:20:47
106.37.222.110	attack	SSH brutforce	2020-08-27 21:43:46
60.249.82.121	attack	Aug 27 15:50:26 abendstille sshd\[758\]: Invalid user www from 60.249.82.121 Aug 27 15:50:26 abendstille sshd\[758\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.249.82.121 Aug 27 15:50:28 abendstille sshd\[758\]: Failed password for invalid user www from 60.249.82.121 port 53584 ssh2 Aug 27 15:55:06 abendstille sshd\[5726\]: Invalid user mozart from 60.249.82.121 Aug 27 15:55:06 abendstille sshd\[5726\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.249.82.121 ...	2020-08-27 22:00:16
167.114.3.158	attackbots	SSH_scan	2020-08-27 22:05:14
41.200.135.59	attackbots	Brute Force	2020-08-27 22:01:29
23.90.29.103	attackspam	(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mtjulietchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwar	2020-08-27 21:55:46
85.209.0.100	attack	Aug 27 14:35:22 server2 sshd\[28427\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers Aug 27 14:35:23 server2 sshd\[28430\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers Aug 27 14:35:24 server2 sshd\[28428\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers Aug 27 14:35:24 server2 sshd\[28431\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers Aug 27 14:35:25 server2 sshd\[28432\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers Aug 27 14:35:26 server2 sshd\[28429\]: User root from 85.209.0.100 not allowed because not listed in AllowUsers	2020-08-27 21:32:32
45.230.45.69	attackspam	Unauthorized connection attempt from IP address 45.230.45.69 on Port 445(SMB)	2020-08-27 21:47:23
189.154.231.240	attackbotsspam	Unauthorized connection attempt from IP address 189.154.231.240 on Port 445(SMB)	2020-08-27 21:28:11
87.117.178.105	attackspambots	Aug 27 11:44:36 scw-tender-jepsen sshd[20479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.117.178.105 Aug 27 11:44:38 scw-tender-jepsen sshd[20479]: Failed password for invalid user webmaster from 87.117.178.105 port 59980 ssh2	2020-08-27 21:30:38
51.75.255.250	attackbots	$f2bV_matches	2020-08-27 21:49:52

Recently Reported IPs

221.127.174.94	223.191.5.76	175.8.14.51	202.106.189.92
165.220.143.131	224.80.167.166	52.245.93.230	75.205.212.202
234.45.191.119	153.61.212.99	132.73.80.17	125.17.19.124
164.71.162.50	205.238.174.196	167.232.163.219	77.97.4.129
36.23.45.255	180.165.201.120	186.13.176.194	201.216.245.49