Compare domains

Best Best setup on each check. Ties get no mark; failed lookups are not ranked.	Checking github.com Reading DNS, live	Checking gitlab.com Reading DNS, live	Checking bitbucket.org Reading DNS, live
SPFWhich servers may send	github.com	gitlab.com	bitbucket.org
DKIMSignatures on each message	github.com	gitlab.com	bitbucket.org
DMARCWhat happens to forgeries	github.com	gitlab.com	bitbucket.org
Mail serversWhere replies are delivered	github.com	gitlab.com	bitbucket.org
MTA-STSForces TLS for inbound mail	github.com	gitlab.com	bitbucket.org
TLS-RPTReports on failed TLS	github.com	gitlab.com	bitbucket.org
BIMIBrand logo in the inbox	github.com	gitlab.com	bitbucket.org
BlocklistsSpamhaus, SpamCop, Barracuda, PSBL	github.com	gitlab.com	bitbucket.org
Forged mailWhat the records ask receivers to do	github.com	gitlab.com	bitbucket.org
Domains it trustsLapsed ones can be bought	github.com	gitlab.com	bitbucket.org
Allowed addressesListed as able to pass SPF	github.com	gitlab.com	bitbucket.org
ProblemsCritical, high and medium	github.com	gitlab.com	bitbucket.org

Best Best setup on each check. Ties get no mark; failed lookups are not ranked.	github.com Microsoft 365 Checked 10 Nov, 00:07 UTC Checking github.com Reading DNS, live	gitlab.com Google Workspace Checked 10 Nov, 00:07 UTC Checking gitlab.com Reading DNS, live	bitbucket.org Proofpoint Checked 10 Nov, 00:07 UTC Checking bitbucket.org Reading DNS, live
SPFWhich servers may send	github.comSoft fail for others (good)10 of 10 lookups used	gitlab.comSoft fail for others (good)1 of 10 lookups used	bitbucket.orgHard fail for others (good)6 of 10 lookups used
DKIMSignatures on each message	github.com8 keys, strongest 2048-bit (good)	gitlab.com3 keys, strongest 1024-bit (needs work)2048-bit is recommended	bitbucket.orgNot confirmed (optional)DNS cannot list selector names
DMARCWhat happens to forgeries	github.comQuarantine, 100% of mail (good)Forgeries go to spam	gitlab.comReject, 100% of mail (good)Forgeries are refused	bitbucket.orgReject, 100% of mail (good)Forgeries are refused
Mail serversWhere replies are delivered	github.comMicrosoft 365 (good)1 host	gitlab.comGoogle Workspace (good)5 hosts	bitbucket.orgProofpoint (good)2 hosts
MTA-STSForces TLS for inbound mailAll 3 have no MTA-STS	github.comNot published (optional)	gitlab.comNot published (optional)	bitbucket.orgNot published (optional)
TLS-RPTReports on failed TLSAll 3 have no TLS reporting	github.comNot published (optional)	gitlab.comNot published (optional)	bitbucket.orgNot published (optional)
BIMIBrand logo in the inboxAll 3 show no brand logo	github.comNot published (optional)	gitlab.comNot published (optional)	bitbucket.orgNot published (optional)
BlocklistsSpamhaus, SpamCop, Barracuda, PSBL	github.comClear on 5 lists (good)	gitlab.comClear on 5 lists (good)	bitbucket.orgClear on 5 lists (good)
Forged mailWhat the records ask receivers to do	github.comSpam folder (needs work)Weakest route: forge your address	gitlab.comRefused (good)On all three routes tried on paper	bitbucket.orgRefused (good)On all three routes tried on paper
Domains it trustsLapsed ones can be bought	github.comAll still registered (good)7 outside domains	gitlab.comAll still registered (good)2 outside domains	bitbucket.orgAll still registered (good)8 outside domains
Allowed addressesListed as able to pass SPF	github.com932,421 IPv4 addresses (optional)Plus 11 IPv6 ranges, 1 hostname known only when mail arrives	gitlab.com0 IPv4 addresses (optional)Plus 1 hostname known only when mail arrives	bitbucket.org223,252 IPv4 addresses (optional)Plus 2 hostnames known only when mail arrives
ProblemsCritical, high and medium	github.comNone serious (good)	gitlab.comNone serious (good)	bitbucket.orgNone serious (good)

SPFWhich servers may send

github.comSoft fail for others10 of 10 lookups used

gitlab.comSoft fail for others1 of 10 lookups used

bitbucket.orgHard fail for others6 of 10 lookups used

DKIMSignatures on each message

github.com8 keys, strongest 2048-bit

gitlab.com3 keys, strongest 1024-bit2048-bit is recommended

bitbucket.orgNot confirmedDNS cannot list selector names

DMARCWhat happens to forgeries

github.comQuarantine, 100% of mailForgeries go to spam

gitlab.comReject, 100% of mailForgeries are refused

bitbucket.orgReject, 100% of mailForgeries are refused

Mail serversWhere replies are delivered

github.comMicrosoft 3651 host

gitlab.comGoogle Workspace5 hosts

bitbucket.orgProofpoint2 hosts

MTA-STSForces TLS for inbound mailAll 3 have no MTA-STS

github.comNot published

gitlab.comNot published

bitbucket.orgNot published

TLS-RPTReports on failed TLSAll 3 have no TLS reporting

github.comNot published

gitlab.comNot published

bitbucket.orgNot published

BIMIBrand logo in the inboxAll 3 show no brand logo

github.comNot published

gitlab.comNot published

bitbucket.orgNot published

BlocklistsSpamhaus, SpamCop, Barracuda, PSBL

github.comClear on 5 lists

gitlab.comClear on 5 lists

bitbucket.orgClear on 5 lists

Forged mailWhat the records ask receivers to do

github.comSpam folderWeakest route: forge your address

gitlab.comRefusedOn all three routes tried on paper

bitbucket.orgRefusedOn all three routes tried on paper

Domains it trustsLapsed ones can be bought

github.comAll still registered7 outside domains

gitlab.comAll still registered2 outside domains

bitbucket.orgAll still registered8 outside domains

Allowed addressesListed as able to pass SPF

github.com932,421 IPv4 addressesPlus 11 IPv6 ranges, 1 hostname known only when mail arrives

gitlab.com0 IPv4 addressesPlus 1 hostname known only when mail arrives

bitbucket.org223,252 IPv4 addressesPlus 2 hostnames known only when mail arrives

ProblemsCritical, high and medium

github.comNone serious

gitlab.comNone serious

bitbucket.orgNone serious