203.211.213.134

Basic Info

City: unknown

Region: unknown

Country: Japan

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

;; QUESTION SECTION:
;203.211.213.134.		IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 09 05:04:52 CST 2024
;; MSG SIZE  rcvd: 108

Host info

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

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

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

Related IP info:

Related comments:

IP	Type	Details	Datetime
217.61.20.238	attackspam	Port scan attempt detected by AWS-CCS, CTS, India	2019-08-24 20:10:53
54.36.126.81	attack	Invalid user neil from 54.36.126.81 port 58550	2019-08-24 20:06:11
174.138.9.132	attack	firewall-block, port(s): 714/tcp	2019-08-24 20:16:38
54.37.199.254	attack	22/tcp [2019-08-24]1pkt	2019-08-24 20:32:25
106.52.89.128	attack	2019-08-24T12:55:24.932988abusebot-8.cloudsearch.cf sshd\[13443\]: Invalid user yu from 106.52.89.128 port 53698	2019-08-24 21:03:19
186.59.111.116	attack	Unauthorised access (Aug 24) SRC=186.59.111.116 LEN=40 TOS=0x10 PREC=0x40 TTL=53 ID=59331 TCP DPT=8080 WINDOW=59815 SYN	2019-08-24 20:42:57
49.234.74.45	attack	Aug 24 01:24:12 web9 sshd\[20626\]: Invalid user bg from 49.234.74.45 Aug 24 01:24:12 web9 sshd\[20626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.74.45 Aug 24 01:24:14 web9 sshd\[20626\]: Failed password for invalid user bg from 49.234.74.45 port 37522 ssh2 Aug 24 01:29:33 web9 sshd\[21727\]: Invalid user collins from 49.234.74.45 Aug 24 01:29:33 web9 sshd\[21727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.74.45	2019-08-24 21:00:58
118.25.27.67	attackspam	Automated report - ssh fail2ban: Aug 24 14:31:11 authentication failure Aug 24 14:31:13 wrong password, user=jin, port=37380, ssh2 Aug 24 14:36:07 authentication failure	2019-08-24 20:56:44
144.48.4.238	attack	Aug 24 14:06:34 dedicated sshd[12293]: Invalid user iva from 144.48.4.238 port 35500	2019-08-24 20:09:24
37.59.53.22	attack	Aug 24 13:20:37 icinga sshd[40252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.53.22 Aug 24 13:20:39 icinga sshd[40252]: Failed password for invalid user tester from 37.59.53.22 port 56436 ssh2 Aug 24 13:29:45 icinga sshd[47085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.53.22 ...	2019-08-24 20:51:51
81.22.45.72	attackbots	Port scan attempt detected by AWS-CCS, CTS, India	2019-08-24 20:10:32
132.232.32.228	attackspambots	Aug 24 07:29:44 Tower sshd[23368]: Connection from 132.232.32.228 port 46612 on 192.168.10.220 port 22 Aug 24 07:29:46 Tower sshd[23368]: Invalid user identd from 132.232.32.228 port 46612 Aug 24 07:29:46 Tower sshd[23368]: error: Could not get shadow information for NOUSER Aug 24 07:29:46 Tower sshd[23368]: Failed password for invalid user identd from 132.232.32.228 port 46612 ssh2 Aug 24 07:29:46 Tower sshd[23368]: Received disconnect from 132.232.32.228 port 46612:11: Bye Bye [preauth] Aug 24 07:29:46 Tower sshd[23368]: Disconnected from invalid user identd 132.232.32.228 port 46612 [preauth]	2019-08-24 20:43:55
59.72.109.242	attackspam	2019-08-24T12:01:11.105540abusebot.cloudsearch.cf sshd\[26732\]: Invalid user web1 from 59.72.109.242 port 51207	2019-08-24 20:48:12
220.82.185.163	attackspambots	SSHScan	2019-08-24 20:37:14
77.247.110.216	attack	\[2019-08-24 08:57:48\] NOTICE\[1829\] chan_sip.c: Registration from '"700" \' failed for '77.247.110.216:5737' - Wrong password \[2019-08-24 08:57:48\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-24T08:57:48.401-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="700",SessionID="0x7f7b302cefa8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.216/5737",Challenge="713cd5d8",ReceivedChallenge="713cd5d8",ReceivedHash="cef9e69ab322c469f70084a7cdb77e21" \[2019-08-24 08:57:48\] NOTICE\[1829\] chan_sip.c: Registration from '"700" \' failed for '77.247.110.216:5737' - Wrong password \[2019-08-24 08:57:48\] SECURITY\[1837\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-24T08:57:48.529-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="700",SessionID="0x7f7b3006b5b8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/7	2019-08-24 20:59:20

Recently Reported IPs

66.252.105.134	49.216.66.59	86.25.210.221	188.34.15.104
115.42.85.29	146.196.242.142	147.25.77.234	23.61.153.99
135.195.28.78	240.175.242.44	186.192.171.99	248.204.115.41
155.147.179.122	35.52.148.20	9.231.220.213	13.43.121.66
126.59.236.184	116.56.241.196	127.83.174.143	39.200.240.166