Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Groww

groww.in
🏆Rank #1,319 🏷 Finance 🇮🇳India ✓ Inbox 89%

Groww uses Pepipost as their primary email service provider. They rank #1,319 in the Tranco list of most-popular domains. We've also observed sends via Amazon SES. Email goes out from 3 different subdomains. Their email authentication setup is solid (score 95/100).

Transactional ESPPepipost
Total observations19
Active days11
Avg per active day1.7
Last activity📬 Active · 5 days ago
Cadence~every 3 days
Compare Groww with another brand:

Email setup 95/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.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
95/100
SPF
pass
DKIM
pass
DMARC
pass (quarantine)
BIMI
verified VMC
Unsubscribe
one-click
SPF lookups 4/10

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

Authentication

DMARC reports sent to groww.in. Policy p=quarantine means receivers actively block or quarantine spoofed mail.

SPF alignment: 63% of observed emails use an aligned return-path (delivery.digest.groww.in, delivery.groww.in); the rest use third-party paths (ap-south-1.amazonses.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 19 observed emails sign with a domain aligned with groww.in (digest.groww.in, daily.digest.groww.in, groww.in). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

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

Other ESPs detected

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

Amazon SES 7

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.

Amazon SES ✓ confirmed Pepipost ✓ 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

Probed: groww.in, delivery.digest.groww.in, ap-south-1.amazonses.com, delivery.groww.in, digest.groww.in, daily.digest.groww.in, 73.groww.in, 84.groww.in, 82.groww.in, 83.groww.in, 74.groww.in

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 17 89.5%
promotions 2 10.5%

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 %
Amazon SES 7
100.0% 0.0% 0.0%
Pepipost 12
83.3% 16.7% 0.0%

ESP activity over time

Jun 1 – Jun 26, 2026 · 11 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.

1 0 Pepipost: 1 (2026-06-01)1Amazon SES: 1 (2026-06-03)1Pepipost: 1 (2026-06-04)1Pepipost: 1 (2026-06-05)1Pepipost: 1 (2026-06-07)1Amazon SES: 1 (2026-06-08)1Amazon SES: 1 (2026-06-09)1Amazon SES: 1 (2026-06-14)1Amazon SES: 1 (2026-06-17)1Pepipost: 1 (2026-06-22)1Pepipost: 1 (2026-06-26)106/0106/0406/0706/1006/1306/1606/1906/2206/25
Pepipost Amazon SES

Similar brands using Pepipost

Sending IPs

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

IPHostnameObsPlacementReputation
150.129.232.84 fallbackmta-232.84.groww.in 3 Check →
150.129.232.74 fallbackmta-232.74.groww.in 3 2 Check →
150.129.232.82 fallbackmta-232.82.groww.in 2 Check →
150.129.232.83 fallbackmta-232.83.groww.in 2 Check →
76.223.181.138 c181-138.smtp-out.ap-south-1.amazonses.com 2 Check →
76.223.181.148 c181-148.smtp-out.ap-south-1.amazonses.com 2 Check →
150.129.232.73 fallbackmta-232.73.groww.in 1 Check →
76.223.181.134 c181-134.smtp-out.ap-south-1.amazonses.com 1 Check →
150.129.232.76 fallbackmta-232.76.digest.groww.in 1 Check →
76.223.181.145 c181-145.smtp-out.ap-south-1.amazonses.com 1 Check →
76.223.181.149 c181-149.smtp-out.ap-south-1.amazonses.com 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
digest.groww.inPepipost 11
daily.digest.groww.inAmazon SES 7
groww.inPepipost 1