Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Getbrick

getbrick.app
🏆Rank N/A 🏷 SaaS 📥 Inbox 54%

Getbrick uses Klaviyo as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPKlaviyo
Total observations128
Active days29
Avg per active day4.4
Last activity📬 Active · 9 days ago
Cadence~weekly

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder Beefree SDK
Interested in using Klaviyo?
Learn about the pros and cons at .
Read the review →
Compare Getbrick with another brand:

Email setup 73/100

Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.

Solid setup, room to improve
Most authentication signals are present. A couple of pieces would tighten things up.
73/100
SPF
pass
DKIM
pass
DMARC
pass (none)
BIMI
none
Unsubscribe
one-click
SPF lookups 2/10

SPF / DKIM / DMARC above reflect the last 10 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to dmarcian. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: all 122 observed emails use a return-path aligned with getbrick.app (k3.email.getbrick.app, k1.email.getbrick.app). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 89 observed emails sign with a domain aligned with getbrick.app (email.getbrick.app). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: modern — 100% TLS 1.3 (across 14 sends).

Delivery (last 7 days): 67% under 10 seconds, 0% over 1 minute (across 3 sends).

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.

Klaviyo ✓ confirmed

Other SPF authorizations

ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.

Google Workspace SendGrid

Probed: getbrick.app, k3.email.getbrick.app, k1.email.getbrick.app

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 33 54.1%
promotions 28 45.9%

Placement by ESP

Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.

ESP Emails Placement Inbox % Tabs % Spam %
Klaviyo 58
55.2% 44.8% 0.0%

ESP activity over time

Jun 1 – Jun 22, 2026 · 12 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

11 0 Klaviyo: 11 (2026-06-01)11Klaviyo: 5 (2026-06-02)5Klaviyo: 2 (2026-06-03)2Klaviyo: 2 (2026-06-04)2Klaviyo: 2 (2026-06-05)2Klaviyo: 2 (2026-06-06)2Klaviyo: 8 (2026-06-09)8Klaviyo: 2 (2026-06-11)2Klaviyo: 3 (2026-06-13)3Klaviyo: 2 (2026-06-15)2Klaviyo: 1 (2026-06-18)1Klaviyo: 1 (2026-06-22)106/0106/0406/0706/1006/1306/1606/1906/22
Klaviyo

Similar brands using Klaviyo

Sending IPs

IP addresses getbrick.app has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsPlacementReputation
170.203.16.2 kl-203-16-2.kmta.shared.klaviyomail.com 19 1 Check →
170.203.24.10 kl-203-24-10.kmta.shared.klaviyomail.com 15 Check →
170.203.27.80 kl-203-27-80.kmta.shared.klaviyomail.com 13 Check →
170.203.20.12 kl-203-20-12.kmta.shared.klaviyomail.com 12 1 Check →
170.203.20.51 kl-203-20-51.kmta.shared.klaviyomail.com 11 Check →
170.203.16.51 kl-203-16-51.kmta.shared.klaviyomail.com 10 1 Check →
170.203.24.2 kl-203-24-2.kmta.shared.klaviyomail.com 9 Check →
170.203.28.28 kl-203-28-28.kmta.shared.klaviyomail.com 6 Check →
170.203.28.37 kl-203-28-37.kmta.shared.klaviyomail.com 6 Check →
149.72.240.239 o1393.shared.klaviyomail.com 6 Check →
170.203.28.36 kl-203-28-36.kmta.shared.klaviyomail.com 4 Check →
170.203.20.2 kl-203-20-2.kmta.shared.klaviyomail.com 4 Check →
170.203.20.221 kl-203-20-221.kmta.shared.klaviyomail.com 4 2 Check →
170.203.31.162 kl-203-31-162.kmta.shared.klaviyomail.com 3 Check →
170.203.16.15 kl-203-16-15.kmta.shared.klaviyomail.com 3 Check →
170.203.24.12 kl-203-24-12.kmta.shared.klaviyomail.com 3 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
getbrick.appKlaviyo 128