Mail domain report: razorpay.com

SPF

warn

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:fdspfus.freshemail.io include:fdspfeuc.freshemail.io include:fdspfind.freshemail.io include:fdspfaus.freshemail.io ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 ip4:34.142.221.122/32 ip4:35.240.151.59/32 exists:%{i}._spf.mta.salesforce.com ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:141.193.32.0/23 ip4:159.135.140.80/29 ip4:159.135.132.128/25 ip4:161.38.204.0/22 ip4:87.253.232.0/21 ip4:185.189.236.0/22 ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:143.55.236.0/22 ip4:198.244.60.0/22 ip4:204.220.160.0/21 ip4:45.115.119.0/24 ip4:123.108.45.122 ip4:123.108.45.123 ip4:123.108.45.112 ip4:202.6.80.0/24 ip4:115.112.174.86 ip4:123.108.33.128/26 ip4:103.57.17.249 ip4:27.0.200.0/24 ip4:27.0.201.0/24 ip4:27.0.202.0/24 ip4:203.153.208.0/24 ip4:103.250.30.1 ip4:103.44.221.0/24 ip4:123.108.43.208/28 ip4:103.57.16.0/22 ip4:103.207.100.22 ip4:103.207.100.23 ip4:103.207.100.24 ip4:103.207.100.25 ip4:103.207.100.26 ip4:115.114.108.245 ip4:103.57.17.0/24 ip4:103.57.18.0/24 ip4:103.57.19.0/24 -all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 6 of 10 DNS lookups #2

SPF record needs 6 DNS lookups (limit is 10).
✓ Ends with -all #3

SPF record properly uses -all to restrict unauthorized senders.
✓ Record published #6

SPF record exists for this domain.
✓ Single record #16

Exactly one SPF record is published.
✓ Valid syntax #25

All SPF mechanisms and modifiers are valid.
✓ No void lookups #26

All include/redirect targets exist.
!

Broad IP ranges

These ranges authorize tens of thousands of addresses or more: ip4:40.92.0.0/15, ip4:52.100.0.0/15. Check that you really own and send from all of them.

#27

DMARC

warn

p=quarantine (_dmarc.razorpay.com)

Found

Record: v=DMARC1; p=quarantine;
Found at: _dmarc.razorpay.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Applies to 100% of mail #18

DMARC policy applies to all failing mail.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.

DKIM

warn

Selectors: mail, k1, google

Found

Selectors: mail, k1, google
_domainkey: NXDOMAIN

Selector	Key	Flags
mail	RSA 1024 bits
k1	RSA 1024 bits
google	RSA 1024 bits

Checks

✓ Keys found: mail, k1, google #7

DKIM keys found for this domain with selectors: mail, k1, google
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits), google (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

pass

5 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.27 AAAA 2a00:1450:4025:c01::1b	rd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.26 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f26.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1b	ncboms-in-f27.1e100.net ✓ ncboms-in-f27.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1a	lcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

✓ 5 MX records #9

Found 5 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
✓ Redundant MX hosts #12

Found 5 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 5 MX records, which is within the recommended range (1-5).
✓ No localhost targets #14

No MX records pointing to localhost found.
✓ No private IP addresses #15

No MX records resolving to private IP addresses found.
✓ No CNAME targets #22

No MX records point to a CNAME.
✓ Reverse DNS confirmed #30

All 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 5 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.com	none	-

Checks

!

Not configured

MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#35
i

Not used

No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.

#36

BIMI

pass

https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.svg

Found

Record: v=BIMI1; l=https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.svg; a=https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.pem
Found at: default._bimi.razorpay.com
Logo: https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.svg
Certificate: https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.svg; certificate: https://vmc.digicert.com/e7916080-01fa-4801-96fd-9113f17ebada.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.