City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 30.0.0.0 - 30.255.255.255
CIDR: 30.0.0.0/8
NetName: DNIC-NET-030
NetHandle: NET-30-0-0-0-1
Parent: ()
NetType: Direct Allocation
OriginAS:
Organization: United States Department of Defense (DoD) (USDDD)
RegDate: 1991-07-01
Updated: 2025-09-05
Ref: https://rdap.arin.net/registry/ip/30.0.0.0
OrgName: United States Department of Defense (DoD)
OrgId: USDDD
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate: 2007-01-12
Updated: 2026-08-12
Ref: https://rdap.arin.net/registry/entity/USDDD
OrgNOCHandle: MIL-HSTMST-ARIN
OrgNOCName: Network DoD
OrgNOCPhone: +1-844-347-2457
OrgNOCEmail: disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil
OrgNOCRef: https://rdap.arin.net/registry/entity/MIL-HSTMST-ARIN
OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: +1-844-347-2457
OrgTechEmail: disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil
OrgTechRef: https://rdap.arin.net/registry/entity/MIL-HSTMST-ARIN
OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: +1-844-347-2457
OrgTechEmail: disa.columbus.ns.mbx.arin-registrations@mail.mil
OrgTechRef: https://rdap.arin.net/registry/entity/REGIS10-ARIN
OrgAbuseHandle: MIL-HSTMST-ARIN
OrgAbuseName: Network DoD
OrgAbusePhone: +1-844-347-2457
OrgAbuseEmail: disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil
OrgAbuseRef: https://rdap.arin.net/registry/entity/MIL-HSTMST-ARIN
# end
# start
NetRange: 30.0.0.0 - 30.255.255.255
CIDR: 30.0.0.0/8
NetName: DNIC-NET-030
NetHandle: NET-30-0-0-0-2
Parent: DNIC-NET-030 (NET-30-0-0-0-1)
NetType: Reallocated
OriginAS:
Organization: DoD Network Information Center (DNIC)
RegDate: 2025-09-05
Updated: 2025-09-05
Ref: https://rdap.arin.net/registry/ip/30.0.0.0
OrgName: DoD Network Information Center
OrgId: DNIC
Address: 3990 E. Broad Street
City: Columbus
StateProv: OH
PostalCode: 43218
Country: US
RegDate:
Updated: 2025-03-13
Ref: https://rdap.arin.net/registry/entity/DNIC
OrgTechHandle: MIL-HSTMST-ARIN
OrgTechName: Network DoD
OrgTechPhone: +1-844-347-2457
OrgTechEmail: disa.columbus.ns.mbx.hostmaster-dod-nic@mail.mil
OrgTechRef: https://rdap.arin.net/registry/entity/MIL-HSTMST-ARIN
OrgAbuseHandle: REGIS10-ARIN
OrgAbuseName: Registration
OrgAbusePhone: +1-844-347-2457
OrgAbuseEmail: disa.columbus.ns.mbx.arin-registrations@mail.mil
OrgAbuseRef: https://rdap.arin.net/registry/entity/REGIS10-ARIN
OrgTechHandle: REGIS10-ARIN
OrgTechName: Registration
OrgTechPhone: +1-844-347-2457
OrgTechEmail: disa.columbus.ns.mbx.arin-registrations@mail.mil
OrgTechRef: https://rdap.arin.net/registry/entity/REGIS10-ARIN
# end
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 30.45.63.252
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26439
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;30.45.63.252. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091901 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Sep 20 10:13:12 CST 2026
;; MSG SIZE rcvd: 105Host 252.63.45.30.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 252.63.45.30.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 64.227.70.114 | attackspam | (sshd) Failed SSH login from 64.227.70.114 (NL/Netherlands/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 28 14:40:30 amsweb01 sshd[18305]: Invalid user fake from 64.227.70.114 port 33774 Feb 28 14:40:32 amsweb01 sshd[18305]: Failed password for invalid user fake from 64.227.70.114 port 33774 ssh2 Feb 28 14:40:32 amsweb01 sshd[18312]: User admin from 64.227.70.114 not allowed because not listed in AllowUsers Feb 28 14:40:32 amsweb01 sshd[18312]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.227.70.114 user=admin Feb 28 14:40:34 amsweb01 sshd[18312]: Failed password for invalid user admin from 64.227.70.114 port 41298 ssh2 |
2020-02-28 22:17:02 |
| 91.244.74.13 | attack | Unauthorized connection attempt from IP address 91.244.74.13 on Port 445(SMB) |
2020-02-28 22:58:59 |
| 112.85.42.173 | attackbots | 2020-02-28T15:22:20.638198scmdmz1 sshd[13668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173 user=root 2020-02-28T15:22:22.763461scmdmz1 sshd[13668]: Failed password for root from 112.85.42.173 port 28915 ssh2 2020-02-28T15:22:26.078407scmdmz1 sshd[13668]: Failed password for root from 112.85.42.173 port 28915 ssh2 2020-02-28T15:22:20.638198scmdmz1 sshd[13668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173 user=root 2020-02-28T15:22:22.763461scmdmz1 sshd[13668]: Failed password for root from 112.85.42.173 port 28915 ssh2 2020-02-28T15:22:26.078407scmdmz1 sshd[13668]: Failed password for root from 112.85.42.173 port 28915 ssh2 2020-02-28T15:22:20.638198scmdmz1 sshd[13668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.173 user=root 2020-02-28T15:22:22.763461scmdmz1 sshd[13668]: Failed password for root from 112.85.42.173 port 28915 ssh2 2020-02-2 |
2020-02-28 22:32:56 |
| 218.201.14.134 | attackbots | Unauthorized connection attempt from IP address 218.201.14.134 on Port 143(IMAP) |
2020-02-28 22:35:25 |
| 54.37.154.113 | attack | Feb 28 15:14:14 vps691689 sshd[22842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.154.113 Feb 28 15:14:16 vps691689 sshd[22842]: Failed password for invalid user administrator from 54.37.154.113 port 44566 ssh2 ... |
2020-02-28 22:27:56 |
| 176.41.5.66 | attackbots | Unauthorized connection attempt from IP address 176.41.5.66 on Port 445(SMB) |
2020-02-28 23:00:42 |
| 45.238.121.153 | attackspambots | Autoban 45.238.121.153 AUTH/CONNECT |
2020-02-28 22:42:51 |
| 113.167.183.68 | attackspambots | Unauthorized connection attempt from IP address 113.167.183.68 on Port 445(SMB) |
2020-02-28 22:54:38 |
| 107.172.148.71 | attackbotsspam | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - christianchiropractic.net - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across christianchiropractic.net, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally lo |
2020-02-28 22:27:36 |
| 23.90.46.218 | attackbotsspam | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - christianchiropractic.net - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across christianchiropractic.net, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally lo |
2020-02-28 22:22:18 |
| 185.36.81.23 | attackbotsspam | Feb 28 14:21:55 mail postfix/smtpd\[20233\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Feb 28 14:54:34 mail postfix/smtpd\[21570\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Feb 28 15:06:40 mail postfix/smtpd\[21570\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Feb 28 15:27:27 mail postfix/smtpd\[22232\]: warning: unknown\[185.36.81.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ |
2020-02-28 22:32:04 |
| 178.128.86.127 | attackbots | Feb 28 14:37:40 hcbbdb sshd\[13384\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.86.127 user=root Feb 28 14:37:42 hcbbdb sshd\[13384\]: Failed password for root from 178.128.86.127 port 37316 ssh2 Feb 28 14:42:05 hcbbdb sshd\[13824\]: Invalid user himanshu from 178.128.86.127 Feb 28 14:42:05 hcbbdb sshd\[13824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.86.127 Feb 28 14:42:07 hcbbdb sshd\[13824\]: Failed password for invalid user himanshu from 178.128.86.127 port 42710 ssh2 |
2020-02-28 22:48:41 |
| 222.186.175.154 | attackbots | 2020-02-28T14:17:29.748782homeassistant sshd[32737]: Failed none for root from 222.186.175.154 port 48718 ssh2 2020-02-28T14:17:30.573919homeassistant sshd[32737]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154 user=root ... |
2020-02-28 22:20:31 |
| 222.186.31.135 | attackspam | Feb 28 15:33:18 vps691689 sshd[23153]: Failed password for root from 222.186.31.135 port 23871 ssh2 Feb 28 15:33:21 vps691689 sshd[23153]: Failed password for root from 222.186.31.135 port 23871 ssh2 Feb 28 15:33:24 vps691689 sshd[23153]: Failed password for root from 222.186.31.135 port 23871 ssh2 ... |
2020-02-28 22:34:59 |
| 59.127.148.148 | attack | suspicious action Fri, 28 Feb 2020 10:32:46 -0300 |
2020-02-28 22:42:39 |