5.112.220.54 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: None

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

;; QUESTION SECTION:
;5.112.220.54.			IN	A

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

;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Apr 06 00:58:52 CST 2022
;; MSG SIZE  rcvd: 105

Host info

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

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

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

Related IP info:

Related comments:

IP	Type	Details	Datetime
34.219.1.184	attackspam	Go-http-client/1.1	2019-06-29 05:50:58
132.232.236.206	attackbotsspam	[FriJun2815:36:15.0200112019][:error][pid19998:tid47129072404224][client132.232.236.206:1809][client132.232.236.206]ModSecurity:Accessdeniedwithcode403$phase2$.Patternmatch"/wp-config.php"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/99_asl_jitp.conf"][line"3411"][id"381206"][rev"1"][msg"Atomicorp.comWAFRules-VirtualJustInTimePatch:AccesstoWordPressconfigurationfileblocked"][data"/wp-config.php"][severity"CRITICAL"][hostname"136.243.224.56"][uri"/wp-config.php"][unique_id"XRYXz@b2FwWmHlVINHhLpgAAABI"][FriJun2815:37:28.8103362019][:error][pid19998:tid47129049290496][client132.232.236.206:12740][client132.232.236.206]ModSecurity:Accessdeniedwithcode404$phase2$.Patternmatch"$\?:/images/stories/\\|/components/com_smartformer/files/\\|/uploaded_files/user/\\|uploads/job-manager-uploads/$.\*\\\\\\\\.php"atREQUEST_URI.[file"/etc/apache2/conf.d/modsec_rules/50_asl_rootkits.conf"][line"71"][id"318812"][rev"2"][msg"Atomicorp.comWAFRules:PossibleAttempttoAccessunauthorized	2019-06-29 05:31:40
27.78.19.215	attackbots	SASL Brute Force	2019-06-29 05:30:13
168.228.148.211	attack	SMTP-sasl brute force ...	2019-06-29 05:19:23
220.163.107.130	attackspambots	$f2bV_matches	2019-06-29 05:25:03
106.13.88.44	attackspambots	$f2bV_matches	2019-06-29 05:46:43
82.64.33.251	attackspam	28.06.2019 13:36:29 SSH access blocked by firewall	2019-06-29 05:50:29
112.222.29.147	attackspam	Jun 28 21:47:40 XXX sshd[30235]: Invalid user davon from 112.222.29.147 port 43936	2019-06-29 05:48:29
185.211.245.198	attack	Jun 28 22:40:25 mail postfix/smtpd\[27177\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jun 28 22:40:36 mail postfix/smtpd\[27177\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jun 28 22:48:19 mail postfix/smtpd\[27231\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Jun 28 23:33:53 mail postfix/smtpd\[28363\]: warning: unknown\[185.211.245.198\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\	2019-06-29 05:34:01
167.99.200.84	attack	Invalid user admin from 167.99.200.84 port 34042	2019-06-29 05:51:45
203.114.196.4	attackbots	Jun 28 16:24:45 s64-1 sshd[25530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.196.4 Jun 28 16:24:47 s64-1 sshd[25530]: Failed password for invalid user vagrant from 203.114.196.4 port 64668 ssh2 Jun 28 16:26:35 s64-1 sshd[25558]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.114.196.4 ...	2019-06-29 05:53:34
5.62.20.29	attack	\[2019-06-28 23:37:05\] NOTICE\[6698\] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '\' failed for '5.62.20.29:4810' $callid: 1212332597-181271954-1975405061$ - Failed to authenticate \[2019-06-28 23:37:05\] SECURITY\[3671\] res_security_log.c: SecurityEvent="ChallengeResponseFailed",EventTV="2019-06-28T23:37:05.441+0200",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="\",SessionID="1212332597-181271954-1975405061",LocalAddress="IPV4/UDP/188.40.118.248/5060",RemoteAddress="IPV4/UDP/5.62.20.29/4810",Challenge="1561757825/5a09e93d871d0ec6dbb9aae6ce30519a",Response="009ba431b84c54a04969a67b0e713671",ExpectedResponse="" \[2019-06-28 23:37:05\] NOTICE\[9010\] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '\' failed for '5.62.20.29:4810' $callid: 1212332597-181271954-1975405061$ - Failed to authenticate \[2019-06-28 23:37:05\] SECURITY\[3671\] res_security_log.c: SecurityEvent="ChallengeResponseFailed",Eve	2019-06-29 05:52:43
180.210.130.20	attack	Jun 28 15:37:57 xeon sshd[41957]: Invalid user test from 180.210.130.20	2019-06-29 05:25:18
91.163.112.140	attackspam	Jun 28 20:02:53 h2177944 sshd\[3210\]: Invalid user victor from 91.163.112.140 port 2169 Jun 28 20:02:53 h2177944 sshd\[3210\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.163.112.140 Jun 28 20:02:55 h2177944 sshd\[3210\]: Failed password for invalid user victor from 91.163.112.140 port 2169 ssh2 Jun 28 20:13:33 h2177944 sshd\[3385\]: Invalid user co from 91.163.112.140 port 2240 Jun 28 20:13:33 h2177944 sshd\[3385\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.163.112.140 ...	2019-06-29 05:22:21
186.224.136.109	attackspambots	SMTP-sasl brute force ...	2019-06-29 05:27:35

Recently Reported IPs

46.227.120.134	28.49.222.10	138.64.193.148	231.217.50.223
24.157.247.44	141.164.192.211	213.129.104.202	62.148.140.206
139.99.238.92	104.129.255.100	151.214.141.180	225.209.231.158
154.29.37.175	231.223.83.58	52.20.199.186	64.81.140.24
224.205.242.161	141.168.32.23	158.13.193.85	86.25.50.32