Vulnerability Scan Result

Target:

http://www.verticalresponse.com/landing/ef/ (redirect)

Scanned target: https://verticalresponse.com/

Submitted: Feb 02, 2026 from NA

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Vertical Response \| Email Marketing Software \| Marketing Automation Tool
Description:	Vertical Response is the Best Platform providing services for Email Marketing, Online Surveys, and Direct Mail for Marketing Campaigns.

IP Information

ip_address	141.193.213.10
country	US
network_name	Cloudflare, Inc.
asn	AS209242

ip_address	141.193.213.11
country	US
network_name	Cloudflare, Inc.
asn	AS209242

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	http	cloudflare -

Web Technologies

Software / Version	Category
Linkedin Insight Tag	Analytics
jQuery CDN	CDN
Contact Form 7 6.1.4	WordPress plugins, Form builders
Google Hosted Libraries	CDN
Elementor 3.35.0	Page builders, WordPress plugins
Facebook Pixel 2.9.256	Analytics
Font Awesome 4.1.0	Font scripts
Bootstrap 3.0.2	UI frameworks
jQuery Migrate 3.3.0	JavaScript libraries
WP-PageNavi	WordPress plugins
parallax.js	JavaScript libraries
core-js 3.39.0	JavaScript libraries
Google Analytics	Analytics
Google Tag Manager for WordPress 1.22.3	WordPress plugins
HTTP/3	Miscellaneous
jQuery 3.7.1	JavaScript libraries
Slick	JavaScript libraries
AOS	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
ProfilePress 4.16.9	WordPress plugins
Select2	JavaScript libraries
Sentry	Issue trackers
Site Kit 1.171.0	Analytics, WordPress plugins
Twitter Emoji (Twemoji)	Font scripts
WordPress	CMS, Blogs
WP Engine	PaaS, Hosting
Cloudflare	CDN
Cloudflare Bot Management	Security
WOW	JavaScript frameworks, Web frameworks, JavaScript graphics
reCAPTCHA	Security
Google Tag Manager	Tag managers
jsDelivr	CDN
Pingdom RUM	RUM
RSS	Miscellaneous
Yoast SEO 26.8	SEO, WordPress plugins
Zendesk	Documentation, Issue trackers, Live chat

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2019-8331	6.1	0.01828	0.82575	In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
CVE-2018-20677	6.1	0.09355	0.92603	In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
CVE-2018-20676	6.1	0.02679	0.85518	In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
CVE-2018-14042	6.1	0.04429	0.88795	In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
CVE-2018-14040	6.1	0.03337	0.87033	In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://verticalresponse.com/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Evidence

Software / Version	Category
Linkedin Insight Tag	Analytics
jQuery CDN	CDN
Contact Form 7 6.1.4	WordPress plugins, Form builders
Google Hosted Libraries	CDN
Elementor 3.35.0	Page builders, WordPress plugins
Facebook Pixel 2.9.256	Analytics
Font Awesome 4.1.0	Font scripts
Bootstrap 3.0.2	UI frameworks
jQuery Migrate 3.3.0	JavaScript libraries
WP-PageNavi	WordPress plugins
parallax.js	JavaScript libraries
core-js 3.39.0	JavaScript libraries
Google Analytics	Analytics
Google Tag Manager for WordPress 1.22.3	WordPress plugins
HTTP/3	Miscellaneous
jQuery 3.7.1	JavaScript libraries
Slick	JavaScript libraries
AOS	JavaScript libraries
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
ProfilePress 4.16.9	WordPress plugins
Select2	JavaScript libraries
Sentry	Issue trackers
Site Kit 1.171.0	Analytics, WordPress plugins
Twitter Emoji (Twemoji)	Font scripts
WordPress	CMS, Blogs
WP Engine	PaaS, Hosting
Cloudflare	CDN
Cloudflare Bot Management	Security
WOW	JavaScript frameworks, Web frameworks, JavaScript graphics
reCAPTCHA	Security
Google Tag Manager	Tag managers
jsDelivr	CDN
Pingdom RUM	RUM
RSS	Miscellaneous
Yoast SEO 26.8	SEO, WordPress plugins
Zendesk	Documentation, Issue trackers, Live chat

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

URL	Evidence
https://verticalresponse.com/	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

Risk description

The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.

Recommendation

Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://verticalresponse.com/	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://verticalresponse.com/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

Risk description

The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.

Recommendation

The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://verticalresponse.com/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://verticalresponse.com/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

Risk description

There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.

Recommendation

We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.

Infrastructure Vulnerabilities

Evidence

DKIM selector	Key type	Key size	Value
zendesk1	rsa	912	"v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9" "NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB"

Vulnerability description

We found that the DKIM key length is under 1024-bit. When a DKIM (DomainKeys Identified Mail) key length is under 1024-bit, it is considered weak by modern cryptographic standards. Shorter key lengths, such as 512 or 768 bits, are vulnerable to brute-force attacks, where an attacker could potentially forge a valid DKIM signature for a domain. This undermines the entire purpose of DKIM, which is to authenticate email messages and prevent email spoofing by verifying that the message headers have not been tampered with. A DKIM key under 1024 bits significantly reduces the difficulty for attackers to break the signature.

Risk description

The primary risk of using a DKIM key with fewer than 1024 bits is that it weakens the domain's email authentication security, making it more susceptible to brute-force attacks. If an attacker successfully forges a DKIM signature, they can impersonate legitimate senders and send fraudulent or phishing emails that appear authentic to the recipient. This can lead to financial losses, reputational damage, and an increased risk of targeted attacks, as recipients are more likely to trust emails that pass DKIM verification.

Recommendation

We recommend using a DKIM key with a length of at least 1024 bits. Ideally, 2048-bit keys should be used, as they provide a higher level of security and are more resistant to brute-force attacks. Organizations should regularly audit their DKIM configurations and rotate cryptographic keys periodically to maintain security. In addition, any DKIM keys that are less than 1024 bits should be immediately replaced with stronger keys to prevent exploitation.

Evidence

DKIM selector	Key type	Key size	Value
dkim	rsa	1362	"v=DKIM1; k=rsa; h=sha256; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvJ7nrHBn5KRBtsiulrmeGxGh5DiC2Wh4/rEZRg1Zl4xYABGNtj3bVWofEy5teWyIPvqgp9SxtWI7rtPCVVkX8x5ENy9VytSgHPw+grPUrfR7b16LWKWlO5Bps/cgm/eFIGNWHENucT3Qf5OjHcKTjf4/6qo90pDaFNVKqMHDyBU6mONisCZ3IP6" "IuvqgZThC9oKaKtgSlcjFWw1ZCxKGM5vSRk4ahIUS/WNjY2IwTrDfqalPdxIlmS8+VeIOGomcEgovxGEUNrhUmH3fN8nWFtWDfpT4Wzd641s37K2RxEJN8n0uffGvuYkOiAwm/H2p9ypbpTbqqLAswB3ya24PUQIDAQAB;"

Vulnerability description

We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.

Risk description

Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.

Recommendation

We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.verticalresponse.com	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:3xfd4vvgq2@rua.app.mailgeeks.com; ruf=mailto:3xfd4vvgq2@ruf.app.mailgeeks.com; adkim=r; aspf=r; ri=86400"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Operating System	Accuracy
FreeBSD 11.1-STABLE	91%

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Domain Queried	DNS Record Type	Description	Value
verticalresponse.com	SPF	Sender Policy Framework	"v=spf1 ip4:74.116.88.0/22 ip4:209.143.92.0/26 include:mail.zendesk.com include:_spf.salesforce.com include:_spf.google.com include:u17235485.wl236.sendgrid.net -all"

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
Cloudflare Bot Management	Security
Cloudflare	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Domain Queried	DNS Record Type	Description	Value
verticalresponse.com	A	IPv4 address	141.193.213.10
verticalresponse.com	A	IPv4 address	141.193.213.11
verticalresponse.com	NS	Name server	demi.ns.cloudflare.com
verticalresponse.com	NS	Name server	james.ns.cloudflare.com
verticalresponse.com	MX	Mail server	1 aspmx.l.google.com
verticalresponse.com	MX	Mail server	10 alt3.aspmx.l.google.com
verticalresponse.com	MX	Mail server	10 alt4.aspmx.l.google.com
verticalresponse.com	MX	Mail server	5 alt1.aspmx.l.google.com
verticalresponse.com	MX	Mail server	5 alt2.aspmx.l.google.com
verticalresponse.com	SOA	Start of Authority	demi.ns.cloudflare.com. dns.cloudflare.com. 2394988184 10000 2400 604800 1800
verticalresponse.com	TXT	Text record	"MS=60FDA41D1A0D1010C909B2150F4F3B93D963B846"
verticalresponse.com	TXT	Text record	"_bpizj1f88etqxh4jbq3hz6zchsi2113"
verticalresponse.com	TXT	Text record	"_mbg44yw1g9gz4u2vg2v1398bqd27l20"
verticalresponse.com	TXT	Text record	"_t42elg62y9y4ouumhixcja9nnn0nwos"
verticalresponse.com	TXT	Text record	"b2bsw578r2gc740110sx9r9922cn9kbw"
verticalresponse.com	TXT	Text record	"google-site-verification=-vIKLd7tCwhRtI0p3ZOxUWO-__avIoWwLk4tT6RS7p4"
verticalresponse.com	SPF	Sender Policy Framework	"v=spf1 ip4:74.116.88.0/22 ip4:209.143.92.0/26 include:mail.zendesk.com include:_spf.salesforce.com include:_spf.google.com include:u17235485.wl236.sendgrid.net -all"
_dmarc.verticalresponse.com	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:3xfd4vvgq2@rua.app.mailgeeks.com; ruf=mailto:3xfd4vvgq2@ruf.app.mailgeeks.com; adkim=r; aspf=r; ri=86400"

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.

Evidence

DKIM selector	Key type	Key size	Value
dkim	rsa	1362	"v=DKIM1; k=rsa; h=sha256; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvJ7nrHBn5KRBtsiulrmeGxGh5DiC2Wh4/rEZRg1Zl4xYABGNtj3bVWofEy5teWyIPvqgp9SxtWI7rtPCVVkX8x5ENy9VytSgHPw+grPUrfR7b16LWKWlO5Bps/cgm/eFIGNWHENucT3Qf5OjHcKTjf4/6qo90pDaFNVKqMHDyBU6mONisCZ3IP6" "IuvqgZThC9oKaKtgSlcjFWw1ZCxKGM5vSRk4ahIUS/WNjY2IwTrDfqalPdxIlmS8+VeIOGomcEgovxGEUNrhUmH3fN8nWFtWDfpT4Wzd641s37K2RxEJN8n0uffGvuYkOiAwm/H2p9ypbpTbqqLAswB3ya24PUQIDAQAB;"
google	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr/xYaQFcQn12gSOEgHMxu4dCp/xoEx/VSqaB+T63NvdmFmyEdoW7AlgQmZA+4IB26qGSRylJZhZve4vY7ZbFJNrLip7XU3H6pOtZeuzSA1ePbnln3y8bCxrukLnJDLGIN9ThwNnlU93i9fNsSROLW74A84F8wDCMJ4FZQFbZnCOOcouieBgkb/MHBTx2GC2iv" "YlF7gQMpo23zuFzwJr5Jtusa1skrd9HkAtnwzvCoEl81/mn8clArPI/LWuPjYug2iE6kit59bEnLOg+jtEEFac+ChFmql+ssiyJDKxu1Fx/Q+ZTnVo1MmI/sADosKrDRnVtcdkduzDOUyyf8P+gsQIDAQAB"
m1	rsa	1296	"k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFUlNZvtGDlIGDRtzyRQydM9yRInD5YMx86QpgZ3v7pT+Mx4tGbjUxY41TXbsp7UH9hTREaKKGQKNM/B3FzcFVv4zafZ09lUaXcbSdtD70iXyH0OXEGXLZI5gG0ZwjK5ptgQ18d+pUP9s8xMkJnZlubTk9MLvQnv3ZBzoL9FHFDQIDAQAB"
zendesk1	rsa	912	"v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9" "NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB"