134.213.40.214

Basic Info

City: unknown

Region: unknown

Country: United Kingdom

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

;; QUESTION SECTION:
;134.213.40.214.			IN	A

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

;; Query time: 127 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 06:00:24 CST 2022
;; MSG SIZE  rcvd: 107

Host info

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

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

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

Related IP info:

Related comments:

IP	Type	Details	Datetime
58.221.101.182	attackbots	Nov 28 23:31:31 itv-usvr-02 sshd[21695]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.221.101.182 user=root Nov 28 23:36:00 itv-usvr-02 sshd[21711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.221.101.182 user=root Nov 28 23:40:12 itv-usvr-02 sshd[21803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.221.101.182	2019-11-29 02:18:47
54.200.115.135	attackbotsspam	2019-11-28 08:33:38 H=ec2-54-200-115-135.us-west-2.compute.amazonaws.com (phylobago.mysecuritycamera.org) [54.200.115.135]:47938 I=[192.147.25.65]:25 sender verify fail for : Unrouteable address 2019-11-28 08:33:38 H=ec2-54-200-115-135.us-west-2.compute.amazonaws.com (phylobago.mysecuritycamera.org) [54.200.115.135]:47938 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed 2019-11-28 08:33:39 H=ec2-54-200-115-135.us-west-2.compute.amazonaws.com (phylobago.mysecuritycamera.org) [54.200.115.135]:47938 I=[192.147.25.65]:25 sender verify fail for : Unrouteable address 2019-11-28 08:33:39 H=ec2-54-200-115-135.us-west-2.compute.amazonaws.com (phylobago.mysecuritycamera.org) [54.200.115.135]:47938 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed ...	2019-11-29 02:14:36
218.92.0.145	attackspam	Nov 28 19:08:03 vmanager6029 sshd\[25130\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.145 user=root Nov 28 19:08:05 vmanager6029 sshd\[25130\]: Failed password for root from 218.92.0.145 port 6531 ssh2 Nov 28 19:08:08 vmanager6029 sshd\[25130\]: Failed password for root from 218.92.0.145 port 6531 ssh2	2019-11-29 02:11:30
106.37.72.234	attackspambots	Nov 26 10:30:14 HOSTNAME sshd[12142]: Address 106.37.72.234 maps to 234.72.37.106.static.bjtelecom.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Nov 26 10:30:14 HOSTNAME sshd[12142]: Invalid user rohani from 106.37.72.234 port 43394 Nov 26 10:30:14 HOSTNAME sshd[12142]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.37.72.234 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=106.37.72.234	2019-11-29 02:12:02
140.143.249.246	attackspambots	(sshd) Failed SSH login from 140.143.249.246 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Nov 28 16:56:08 andromeda sshd[21156]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.249.246 user=root Nov 28 16:56:10 andromeda sshd[21156]: Failed password for root from 140.143.249.246 port 46352 ssh2 Nov 28 17:19:32 andromeda sshd[23665]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.249.246 user=backup	2019-11-29 02:25:57
46.101.171.183	attackspambots	[Thu Nov 28 11:33:38.999052 2019] [:error] [pid 191405] [client 46.101.171.183:61000] [client 46.101.171.183] ModSecurity: Access denied with code 403 (phase 2). Operator GE matched 5 at TX:anomaly_score. [file "/usr/share/modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "91"] [id "949110"] [msg "Inbound Anomaly Score Exceeded (Total Score: 8)"] [severity "CRITICAL"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "ws22vmsma01.ufn.edu.br"] [uri "/"] [unique_id "Xd-awgTlpIctpDm1UAOgIgAAAAA"] ...	2019-11-29 02:14:59
45.122.220.31	attack	Nov 28 03:37:53 mxgate1 postfix/postscreen[18854]: CONNECT from [45.122.220.31]:59756 to [176.31.12.44]:25 Nov 28 03:37:53 mxgate1 postfix/dnsblog[18855]: addr 45.122.220.31 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2 Nov 28 03:37:53 mxgate1 postfix/dnsblog[18858]: addr 45.122.220.31 listed by domain b.barracudacentral.org as 127.0.0.2 Nov 28 03:37:59 mxgate1 postfix/postscreen[18854]: DNSBL rank 2 for [45.122.220.31]:59756 Nov x@x Nov 28 03:38:00 mxgate1 postfix/postscreen[18854]: DISCONNECT [45.122.220.31]:59756 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=45.122.220.31	2019-11-29 01:55:09
185.248.103.114	attackspam	Connection by 185.248.103.114 on port: 23 got caught by honeypot at 11/28/2019 1:34:15 PM	2019-11-29 02:01:44
50.63.166.50	attackspambots	50.63.166.50 - - \[28/Nov/2019:17:55:54 +0100\] "POST /wp-login.php HTTP/1.0" 200 5314 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 50.63.166.50 - - \[28/Nov/2019:17:56:02 +0100\] "POST /wp-login.php HTTP/1.0" 200 5133 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 50.63.166.50 - - \[28/Nov/2019:17:56:05 +0100\] "POST /wp-login.php HTTP/1.0" 200 5137 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"	2019-11-29 02:03:57
115.159.198.178	attackbotsspam	REQUESTED PAGE: /TP/public/index.php	2019-11-29 02:17:23
188.150.168.100	attack	22 attack	2019-11-29 02:24:15
168.181.49.66	attackspambots	Nov 28 17:55:00 v22018086721571380 sshd[28293]: Failed password for invalid user saue from 168.181.49.66 port 22080 ssh2 Nov 28 18:57:04 v22018086721571380 sshd[32214]: Failed password for invalid user nobody000 from 168.181.49.66 port 22139 ssh2	2019-11-29 02:04:11
91.35.223.198	attackspambots	Nov 28 03:33:10 prometheus imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:91.35.223.198] Nov 28 03:33:15 prometheus imapd-ssl: LOGOUT, ip=[::ffff:91.35.223.198], rcvd=86, sent=344 Nov 28 03:33:15 prometheus imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:91.35.223.198] Nov 28 03:33:20 prometheus imapd-ssl: LOGOUT, ip=[::ffff:91.35.223.198], rcvd=74, sent=344 Nov 28 03:33:20 prometheus imapd-ssl: LOGIN FAILED, user=sebastian, ip=[::ffff:91.35.223.198] Nov 28 03:33:25 prometheus imapd-ssl: LOGOUT, ip=[::ffff:91.35.223.198], rcvd=50, sent=340 Nov 28 03:36:19 prometheus imapd-ssl: LOGIN FAILED, method=PLAIN, ip=[::ffff:91.35.223.198] Nov 28 03:36:19 prometheus imapd-ssl: LOGIN, user=sebastian@x Nov 28 03:36:20 prometheus imapd-ssl: LOGIN, user=sebastian@x Nov 28 03:36:20 prometheus imapd-ssl: LOGIN, user=sebastian@x Nov 28 03:36:20 prometheus imapd-ssl: LOGIN, user=sebastian@x Nov 28 03:36:24 prometheus imapd-ssl: LOGOUT, ip=[::ffff:91.35.223.198], rcvd=86, sent=344 No........ -------------------------------	2019-11-29 02:04:45
51.104.237.2	attack	28.11.2019 15:33:50 - RDP Login Fail Detected by https://www.elinox.de/RDP-Wächter	2019-11-29 02:13:40
85.222.97.154	attackbotsspam	Automatic report - Port Scan Attack	2019-11-29 01:49:47

Recently Reported IPs

134.213.31.154	134.213.45.219	134.213.46.99	118.173.132.162
134.213.48.80	134.213.49.87	134.213.49.203	134.213.49.60
134.213.5.204	118.173.132.166	118.173.132.173	118.173.132.176
118.173.132.180	118.173.132.190	118.173.132.206	118.173.132.209
118.173.138.130	118.173.138.19	118.173.138.208	118.173.138.237