Due to unforeseen circumstances with the cloud migration, MeridanLink will be postponing the go-live for August 26, 2022 and rescheduling to Friday, September 9, 2022. We will continue to provide notice as we approach that date.
Please note that this announcement contains new information about what to expect during our production environment migration to our new infrastructure. See below for details.
As a reminder, MeridianLink is performing various improvements to the Mortgage Credit Link and Credit API infrastructure to improve the scale and durability of our services. The dates of these improvements are listed below:
Test Environment: COMPLETED as of June 6, 2022
Production Environment: Friday, September 9, 2022.
What to Expect
Please be advised that MeridianLink Mortgage Credit Link’s production environment will be down for maintenance and unavailable Friday, September 9, 2022, from 8:30 PM PDT to 1:30 AM PDT.
During that time, the Mortgage Credit Link website will be inaccessible. Additionally, any attempts to order or reissue credit or verifications services through an API connection will result in an error.
Systems will be closely monitored once they are online on our new infrastructure. Please reach out to our support teams if you have any questions or problems after the updates are completed at servicing@certifiedcredit.com or ts@certifiedcredit.com.
Actions Required
To ensure continued connectivity to the Mortgage Credit Link and Credit API applications, MeridianLink is requesting that you review the following information and make any necessary changes with your IT team. Failure to make these changes may result in the inability to access our applications or perform critical business functions.
1. Whitelist IP Addresses
First, please verify with your IT department if your organization maintains an IP address whitelist for external applications such as Mortgage Credit Link or Credit API.
If the answer is no, no action is required on your end.
If the answer is yes, please work with your IT department to add the following IP ranges to your whitelist:
198.185.62.0/23
12.106.86.0/24
208.81.32.0/22
52.159.160.192/28
20.184.246.192/29
20.184.246.200/29
20.184.246.176/28
20.184.246.208/28
20.184.246.224/28
20.81.63.240/28
168.61.6.128/25
20.124.173.0/25
20.72.182.80/28
Once these IP addresses are whitelisted, please do not remove any existing IP addresses from your whitelist, to ensure no interruption in connectivity.
2. Update DNS Server
Please verify if your organization sends email from the Mortgage Credit Link platform.
If the answer is no, no action is required on your end.
If the answer is yes, please have your IT team add the following three CNAME records to your DNS server.
1. SPF CNAME record
Key: mlk
Value: mlkspf.esp.meridianlink.com
mlk.example.com should resolve to mlkspf.esp.meridianlink.com, where “example” in the SPF CNAME record would be the client domain. For example, mlk.bluestreamcu.com.
If a client chooses a different custom return path such as mail, the CNAME record should be mail.example.com → mlkspf.esp.meridianlink.com. For example, mail.bluestream.com.
2. DKIM CNAME record 1
Key: mlk._domainkey
Value: mlkdkim.esp.meridianlink.com
mlk._domainkey.example.com should resolve to mlkdkim.esp.meridianlink.com, where “example” in the DKIM CNAME record 1 would be the client domain. For example, mlk._domainkey.bluestreamcu.com.
3. DKIM CNAME record 2
Key: mlk2._domainkey
Value: mlkdkim2.esp.meridianlink.com
mlk2._domainkey.example.com should resolve to mlkdkim2.esp.meridianlink.com, where “example” in the DKIM CNAME record 2 would be the client domain. For example, mlk2._domainkey.bluestreamcu.com.
If you do not send emails from Mortgage Credit Link then no action is needed.
3. Ensure OpenSSL and Apache-HttpClient Support Server Name Indication (SNI)
Next, if you are a Credit API user or an integrating partner with MeridianLink, please verify that your versions of OpenSSL and Apache-HttpClient are up to date and support Server Name Indication (SNI).
If the answer is yes, no action is required on your end.
If the answer is no, please have your IT team upgrade OpenSSL and Apache-HttpClient to ensure SNI is supported.
