minFraud Release Notes - 2019 Archive
The USER_ID_REQUIRED error code is now ACCOUNT_ID_REQUIRED
December 23, 2019ACCOUNT_ID_REQUIRED instead of USER_ID_REQUIRED when the
account ID parameter is missing.Query usage report license key filter
December 17, 2019Toggle minFraud Transactions Access
December 11, 2019Account administrators can now enable or disable access to the minFraud Transactions page [login required], which is accessible from the account portal. You can manage account access to this feature here [login required].
The minFraud Transactions page is used for review, dispositioning, tagging, and exporting transactions. See our guide for more info.
Changes to Japan Postal Codes
December 11, 20191 as the last digit for all 7
digit postal codes in Japan. The last digit refers to street-level
resolution and should not
be relied upon for IP geolocation.Changes to Portugal Postal Codes
November 8, 2019-001 as the last 3 digits for all
7 digit postal codes in Lisbon, Portugal. Our postal code resolution in
Portugal is accurate for the first 4 digits and we include the -001 at the
end for backwards compatibility for customers to join the data with 7 digit
Portuguese postal code databases. We may extend this convention to other large
Portuguese cities in the future.Retirement of TLS 1.0/1.1 and unencrypted http minFraud requests
October 16, 2019New static_ip_score output in web services
October 15, 2019The following output has been added to the GeoIP2 Insights web service, and minFraud Insights and Factors web services:
static_ip_score– An indicator of how static or dynamic an IP address is. The value ranges from 0 to 99.99 with higher values meaning a greater static association. For example, many IPs with auser_typeofcellularhave a score under one. Static Cable/DSL IPs typically have a score above thirty.This indicator can be useful for deciding whether an IP address represents the same user over time.
The static_ip_score output is present in the traits object.
Final reminder of security-related retirements
October 14, 2019This is a reminder that we are retiring support for requests using TLS 1.0/1.1, and unencrypted HTTP requests to MaxMind minFraud services on October 16, 2019. After October 16, 2019, these types of requests will always fail with an error. Please update to TLS 1.2+ to avoid service disruption. You may need to upgrade your technology stack to a later version, or make code changes to do so.
Contact us for support or if you have questions.
Improved cellular IP detection
October 3, 2019connection_type field provided in the GeoIP2 Connection Type
database, and the
user_type field provided in the GeoIP2 Insights web
service and minFraud
services. Accuracy for
cellular identification should now be about 95% accurate globally.Account activity log
October 2, 2019You can now view a log of your MaxMind account activity, which includes a time stamp, requester, and subject, for the each of the following actions:
- Creation of a new user
- Deactivation of a user
- User password changes
- Email address / username changes
Account administrators can see activity across the whole account, while non-administrators will only see their own activity. You can find the account activity log in your account portal under ‘Account Information’ or here [login required].
High risk IP country deprecation
September 30, 2019/ip_address/country/is_high_risk output in minFraud
Insights and minFraud Factors (and highRiskCountry output in
legacy minFraud services) because it provides
limited value. You can find the IP country in the /ip_address/country/names
output.New network and user_count outputs in web services
September 19, 2019The following outputs have been added to the GeoIP2 Insights web service, and minFraud Insights and Factors web services:
network– The network in CIDR notation associated with the record. This is the largest network where all of the fields besidesip_addresshave the same value.user_count– The estimated number of users sharing the IP/network during the past 24 hours. For IPv4, the count is for the individual IP. For IPv6, the count is for the /64 network.
Both of these outputs are present in the traits object.
Planned warning interruption (September 2019)
September 16, 20198-hour interruption of old TLS and unencrypted minFraud requests on September 25, 2019
There will be a planned service interruption for all requests to MaxMind services that use TLS versions 1.0 and 1.1, and for unencrypted HTTP requests to MaxMind legacy minFraud services (e.g. minFraud Standard, minFraud Premium, Proxy Detection web service, IIN service). This will take place for up to 8 hours from 14:00-22:00 UTC on September 25, 2019.
During the interruption, requests using TLS v1.0 and v1.1 and unencrypted HTTP requests to legacy minFraud endpoints will fail with an error.
To avoid service interruption, you may need to upgrade some part of your technology stack to a later version, or you may need to make code changes. If you have any questions, please do not hesitate to contact us. Additional info is available on our blog.
IP and email tenure deprecation
August 29, 2019/subscores/ip_tenure and
subscores/email_tenure risk-factor outputs in the minFraud Factors service
because they provided limited value. The subscores will default to 1 and will
be removed in a future release. The IP tenure is reflected in the overall risk
score. The user tenure on email is reflected in the /subscores/email_address
output.Improved business IP detection
August 21, 2019Planned warning interruption (August 2019)
August 20, 20198-hour interruption of old TLS and unencrypted minFraud requests on August 28, 2019
There will be a planned service interruption for all requests to MaxMind services that use TLS versions 1.0 and 1.1, and for unencrypted HTTP requests to MaxMind legacy minFraud services (e.g. minFraud Standard, minFraud Premium, Proxy Detection web service, IIN service). This will take place for up to 8 hours from 14:00-22:00 UTC on August 28, 2019.
During the interruption, requests using TLS v1.0 and v1.1 and unencrypted HTTP requests to legacy minFraud endpoints will fail with an error.
To avoid service interruption, you may need to upgrade some part of your technology stack to a later version, or you may need to make code changes. If you have any questions, please do not hesitate to contact us. Additional info is available on our blog.
Retirement of legacy IIN (BIN) API service
August 5, 2019We are discontinuing the legacy IIN (BIN) API on January 31, 2020 in order to focus development and maintenance efforts on our core services. This means that the service will no longer function if you are querying the URL below: https://minfraud.maxmind.com/app/bin_http
Please note that we continue to support the IIN (BIN) look-up form on our website [login required], so that remains an option for your use. If you require an API because of volume considerations, we recommend either using our minFraud Insights API (IP address is a required input field) or integrating an alternative commercially available solution.
Planned warning interruption
July 24, 2019There will be a planned service interruption for all requests to MaxMind services that use TLS versions 1.0 and 1.1, and for unencrypted HTTP requests to MaxMind legacy minFraud services (e.g. minFraud Standard, minFraud Premium, Proxy Detection web service, IIN service). This will take place for up to 2 hours starting at 14:00 UTC on the three dates below:
- Monday, July 29, 2019
- Wednesday, July 31, 2019
- Friday, August 2, 2019
During the interruption, requests using TLS v1.0 and v1.1 and unencrypted HTTP requests to legacy minFraud endpoints will fail with an error.
To avoid service interruption, you may need to upgrade some part of your technology stack to a later version, or you may need to make code changes. If you have any questions, please do not hesitate to contact us. Additional info is available on our blog.