Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: South Africa

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 105.221.5.57
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53126
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;105.221.5.57.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 09:15:32 CST 2023
;; MSG SIZE  rcvd: 105
Host info
Host 57.5.221.105.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 57.5.221.105.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
172.93.192.212 attackspambots
(From eric@talkwithcustomer.com) Hello siegelchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website siegelchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website siegelchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as
2019-08-15 17:45:16
94.141.60.243 attack
[portscan] Port scan
2019-08-15 17:21:54
138.36.188.162 attackspam
scan z
2019-08-15 16:55:21
173.218.243.137 attackbotsspam
Invalid user mailserver from 173.218.243.137 port 45872
2019-08-15 17:10:12
190.246.175.156 attack
Aug 15 09:29:32 XXX sshd[48616]: Invalid user test from 190.246.175.156 port 38104
2019-08-15 17:18:13
213.21.67.184 attack
Aug 15 09:29:50 unicornsoft sshd\[13552\]: Invalid user test2 from 213.21.67.184
Aug 15 09:29:50 unicornsoft sshd\[13552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.21.67.184
Aug 15 09:29:52 unicornsoft sshd\[13552\]: Failed password for invalid user test2 from 213.21.67.184 port 58415 ssh2
2019-08-15 17:37:36
187.198.96.128 attackbotsspam
Looking for resource vulnerabilities
2019-08-15 17:22:56
95.48.54.106 attackbotsspam
Automatic report - Banned IP Access
2019-08-15 16:52:04
187.44.113.33 attack
Aug 15 01:22:03 nextcloud sshd\[6144\]: Invalid user rm from 187.44.113.33
Aug 15 01:22:03 nextcloud sshd\[6144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.44.113.33
Aug 15 01:22:05 nextcloud sshd\[6144\]: Failed password for invalid user rm from 187.44.113.33 port 36994 ssh2
...
2019-08-15 17:26:44
121.133.169.254 attack
Aug 15 10:32:15 hosting sshd[5496]: Invalid user deploy from 121.133.169.254 port 60234
...
2019-08-15 16:49:04
5.62.41.113 attackspambots
\[2019-08-15 05:13:24\] NOTICE\[2288\] chan_sip.c: Registration from '\' failed for '5.62.41.113:11771' - Wrong password
\[2019-08-15 05:13:24\] SECURITY\[2326\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-15T05:13:24.358-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="2295",SessionID="0x7ff4d0348688",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/5.62.41.113/56315",Challenge="775e37d3",ReceivedChallenge="775e37d3",ReceivedHash="eb2cb2e787247a12a977993cb78c6b82"
\[2019-08-15 05:22:57\] NOTICE\[2288\] chan_sip.c: Registration from '\' failed for '5.62.41.113:11661' - Wrong password
\[2019-08-15 05:22:57\] SECURITY\[2326\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-08-15T05:22:57.786-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="8174",SessionID="0x7ff4d07952f8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/5.62.41.113/566
2019-08-15 17:23:52
187.58.65.21 attack
Aug 15 02:38:49 vps200512 sshd\[18627\]: Invalid user password from 187.58.65.21
Aug 15 02:38:49 vps200512 sshd\[18627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.58.65.21
Aug 15 02:38:50 vps200512 sshd\[18627\]: Failed password for invalid user password from 187.58.65.21 port 40523 ssh2
Aug 15 02:43:57 vps200512 sshd\[18813\]: Invalid user 123456 from 187.58.65.21
Aug 15 02:43:57 vps200512 sshd\[18813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.58.65.21
2019-08-15 17:20:58
191.101.104.177 attackbotsspam
(From eric@talkwithcustomer.com) Hello siegelchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website siegelchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website siegelchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as
2019-08-15 17:41:42
39.68.63.117 attackspambots
firewall-block, port(s): 8080/tcp
2019-08-15 17:33:53
54.36.148.71 attack
Automatic report - Banned IP Access
2019-08-15 16:46:50

Recently Reported IPs

105.223.231.2 105.222.111.233 105.221.42.69 105.222.149.210
105.223.129.60 105.222.214.53 105.221.62.191 105.222.58.27
105.222.1.35 105.222.163.179 105.222.244.79 105.221.60.118
105.222.148.199 105.222.155.184 105.221.44.24 105.221.155.20
105.221.99.65 105.222.185.32 105.221.17.131 105.222.172.12