City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.9.219
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38091
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.9.219. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021701 1800 900 604800 86400
;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:12:44 CST 2022
;; MSG SIZE rcvd: 105Host 219.9.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 219.9.21.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 59.127.82.236 | attackspambots | Automatic report - Port Scan |
2020-03-05 00:04:17 |
| 115.51.110.252 | attackbotsspam | 23/tcp [2020-03-04]1pkt |
2020-03-05 00:02:05 |
| 217.61.17.134 | attackbots | SSH brute-force: detected 12 distinct usernames within a 24-hour window. |
2020-03-04 23:57:41 |
| 128.199.70.211 | attackspambots | CMS (WordPress or Joomla) login attempt. |
2020-03-04 23:46:40 |
| 23.83.179.208 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjenniferbrandon.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 software t |
2020-03-04 23:40:59 |
| 1.53.30.38 | attack | 81/tcp [2020-03-04]1pkt |
2020-03-04 23:52:36 |
| 222.186.31.166 | attackbotsspam | 2020-03-04T09:15:17.178286homeassistant sshd[23609]: Failed password for root from 222.186.31.166 port 35580 ssh2 2020-03-04T15:54:22.854753homeassistant sshd[2515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166 user=root ... |
2020-03-04 23:57:10 |
| 197.54.175.170 | attackbotsspam | 1583328975 - 03/04/2020 14:36:15 Host: 197.54.175.170/197.54.175.170 Port: 445 TCP Blocked |
2020-03-04 23:44:19 |
| 49.232.17.7 | attack | Mar 4 22:13:49 webhost01 sshd[23618]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.17.7 Mar 4 22:13:50 webhost01 sshd[23618]: Failed password for invalid user pi from 49.232.17.7 port 39580 ssh2 ... |
2020-03-04 23:30:32 |
| 159.203.176.82 | attack | xmlrpc attack |
2020-03-05 00:01:10 |
| 218.246.34.214 | attack | Mar 4 13:28:19 localhost sshd[88737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.246.34.214 user=mysql Mar 4 13:28:21 localhost sshd[88737]: Failed password for mysql from 218.246.34.214 port 38478 ssh2 Mar 4 13:36:00 localhost sshd[89532]: Invalid user lagatagreta from 218.246.34.214 port 36238 Mar 4 13:36:00 localhost sshd[89532]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.246.34.214 Mar 4 13:36:00 localhost sshd[89532]: Invalid user lagatagreta from 218.246.34.214 port 36238 Mar 4 13:36:01 localhost sshd[89532]: Failed password for invalid user lagatagreta from 218.246.34.214 port 36238 ssh2 ... |
2020-03-05 00:11:48 |
| 54.38.129.15 | attackbotsspam | 3389/tcp [2020-03-04]1pkt |
2020-03-04 23:43:00 |
| 221.133.18.119 | attackbots | $f2bV_matches |
2020-03-04 23:49:49 |
| 103.30.180.145 | attack | Mar 4 16:01:25 MK-Soft-VM8 sshd[12221]: Failed password for root from 103.30.180.145 port 53874 ssh2 Mar 4 16:11:19 MK-Soft-VM8 sshd[12437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.30.180.145 ... |
2020-03-04 23:53:49 |
| 139.59.90.0 | attack | Mar 4 16:23:04 srv01 sshd[1798]: Invalid user oracle from 139.59.90.0 port 56610 Mar 4 16:23:04 srv01 sshd[1798]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.90.0 Mar 4 16:23:04 srv01 sshd[1798]: Invalid user oracle from 139.59.90.0 port 56610 Mar 4 16:23:06 srv01 sshd[1798]: Failed password for invalid user oracle from 139.59.90.0 port 56610 ssh2 Mar 4 16:26:42 srv01 sshd[2129]: Invalid user lackz from 139.59.90.0 port 54380 ... |
2020-03-04 23:34:15 |