NetRange: 168.207.0.0 - 168.207.255.255
CIDR: 168.207.0.0/16
NetName: REYNOLDS2
NetHandle: NET-168-207-0-0-1
Parent: NET168 (NET-168-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: The Reynolds and Reynolds Company (THEREY-Z)
RegDate: 1994-07-06
Updated: 2023-07-10
Ref: https://rdap.arin.net/registry/ip/168.207.0.0
OrgName: The Reynolds and Reynolds Company
OrgId: THEREY-Z
Address: One Reynolds Way
City: Kettering
StateProv: OH
PostalCode: 45430
Country: US
RegDate: 2019-02-15
Updated: 2024-04-04
Ref: https://rdap.arin.net/registry/entity/THEREY-Z
OrgTechHandle: BADIN-ARIN
OrgTechName: Bading, Kyle
OrgTechPhone: +1-937-485-2000
OrgTechEmail: KYLE_BADING@REYREY.COM
OrgTechRef: https://rdap.arin.net/registry/entity/BADIN-ARIN
OrgTechHandle: HAGER112-ARIN
OrgTechName: Hager, Jeff
OrgTechPhone: +1-937-485-2000
OrgTechEmail: Jeff_Hager@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/HAGER112-ARIN
OrgTechHandle: HIGGS24-ARIN
OrgTechName: Higgs, DJ
OrgTechPhone: +1-937-485-2000
OrgTechEmail: DJ_Higgs@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/HIGGS24-ARIN
OrgTechHandle: BENYS-ARIN
OrgTechName: Benysek, Jake
OrgTechPhone: +1-937-485-2000
OrgTechEmail: Jake_Benysek@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/BENYS-ARIN
OrgTechHandle: JOSEJ1-ARIN
OrgTechName: Jose, Jiji
OrgTechPhone: +1-937-485-2000
OrgTechEmail: jiji_jose@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/JOSEJ1-ARIN
OrgAbuseHandle: DCG9-ARIN
OrgAbuseName: Data Center Group
OrgAbusePhone: +1-937-485-2000
OrgAbuseEmail: datacenterservices@reyrey.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/DCG9-ARIN
OrgDNSHandle: HEIMP-ARIN
OrgDNSName: Heim, Preston
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: PRESTON_HEIM@REYREY.COM
OrgDNSRef: https://rdap.arin.net/registry/entity/HEIMP-ARIN
OrgDNSHandle: HAGER112-ARIN
OrgDNSName: Hager, Jeff
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: Jeff_Hager@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/HAGER112-ARIN
OrgTechHandle: FUENT112-ARIN
OrgTechName: Fuentes, Edwin
OrgTechPhone: +1-937-485-2000
OrgTechEmail: Edwin_Fuentes@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/FUENT112-ARIN
OrgDNSHandle: BADIN-ARIN
OrgDNSName: Bading, Kyle
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: KYLE_BADING@REYREY.COM
OrgDNSRef: https://rdap.arin.net/registry/entity/BADIN-ARIN
OrgTechHandle: RRNS-ARIN
OrgTechName: Reynolds and Reynolds Network Services
OrgTechPhone: +1-937-485-2000
OrgTechEmail: softwareadmin@reyrey.com
OrgTechRef: https://rdap.arin.net/registry/entity/RRNS-ARIN
OrgDNSHandle: BENYS-ARIN
OrgDNSName: Benysek, Jake
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: Jake_Benysek@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/BENYS-ARIN
OrgTechHandle: HEIMP-ARIN
OrgTechName: Heim, Preston
OrgTechPhone: +1-937-485-2000
OrgTechEmail: PRESTON_HEIM@REYREY.COM
OrgTechRef: https://rdap.arin.net/registry/entity/HEIMP-ARIN
OrgDNSHandle: HIGGS24-ARIN
OrgDNSName: Higgs, DJ
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: DJ_Higgs@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/HIGGS24-ARIN
OrgDNSHandle: JERGE2-ARIN
OrgDNSName: Jergens, Nathan
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: Nathan_Jergens@reyrey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/JERGE2-ARIN
OrgTechHandle: HONNO1-ARIN
OrgTechName: Honnold, Scott
OrgTechPhone: +1-937-485-9823
OrgTechEmail: Scott_Honnold@ReyRey.com
OrgTechRef: https://rdap.arin.net/registry/entity/HONNO1-ARIN
OrgDNSHandle: HONNO1-ARIN
OrgDNSName: Honnold, Scott
OrgDNSPhone: +1-937-485-9823
OrgDNSEmail: Scott_Honnold@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/HONNO1-ARIN
OrgTechHandle: JERGE2-ARIN
OrgTechName: Jergens, Nathan
OrgTechPhone: +1-937-485-2000
OrgTechEmail: Nathan_Jergens@reyrey.com
OrgTechRef: https://rdap.arin.net/registry/entity/JERGE2-ARIN
OrgDNSHandle: JOSEJ1-ARIN
OrgDNSName: Jose, Jiji
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: jiji_jose@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/JOSEJ1-ARIN
OrgDNSHandle: FUENT112-ARIN
OrgDNSName: Fuentes, Edwin
OrgDNSPhone: +1-937-485-2000
OrgDNSEmail: Edwin_Fuentes@ReyRey.com
OrgDNSRef: https://rdap.arin.net/registry/entity/FUENT112-ARIN
RTechHandle: RRNS-ARIN
RTechName: Reynolds and Reynolds Network Services
RTechPhone: +1-937-485-2000
RTechEmail: softwareadmin@reyrey.com
RTechRef: https://rdap.arin.net/registry/entity/RRNS-ARIN
RTechHandle: MOORE1582-ARIN
RTechName: Moore, Darrell
RTechPhone: +1-937-485-2000
RTechEmail: darrell_moore@reyrey.com
RTechRef: https://rdap.arin.net/registry/entity/MOORE1582-ARIN
RTechHandle: MORGA768-ARIN
RTechName: Morgan, Anita
RTechPhone: +1-937-485-2000
RTechEmail: softwareadmin@reyrey.com
RTechRef: https://rdap.arin.net/registry/entity/MORGA768-ARIN
Most recent complaints on 168.207.152.198
No comments submitted yet.
Please help us keep Internet safer and cleaner by leaving a descriptive comment about 168.207.152.198 IP address
IP addresses with same latency:
DNSBL* -
is a list of IP addresses published through the Internet Domain Name Service (DNS) either as a zone file that can be used by DNS server software, or as a live DNS zone
that can be queried in real-time. DNSBLs are most often used to publish the addresses of computers or networks linked to spamming; most mail server software can be
configured to reject or flag messages which have been sent from a site listed on one or more such lists.
WHOIS** - is a query/response protocol that is widely used
for querying databases in order to determine the registrant or assignee of Internet resources, such as a domain name, an
IP address block, or an autonomous system number. WHOIS lookups were traditionally performed with a
command line interface application, and network administrators predominantly still use this method, but many
simplified web-based tools exist. WHOIS services are typically communicated using the Transmission Control Protocol
(TCP). Servers listen to requests on the well-known port number 43.
** Approximate Geographic Location - This is NOT the exact geographical location of
the person/organization with the given IP address. However, this should still give you a good idea about
the area/region where this person/orgranization is located.