DNS & email auth

warnLast checked
Findings6 findings

Recommended (3)

  • DKIM selector selector1 uses a 1024-bit RSA key.

    DKIM

    selector1 (selector1._domainkey.golevo.com)

    How to fix

    Rotate to an RSA key of at least 2048 bits.

  • DMARC policy is p=none, so it monitors but does not enforce.

    DMARC

    How to fix

    Once your legitimate senders pass, move to p=quarantine and then p=reject.

  • The record has no rua= aggregate reporting address, so no one is told when DMARC fails.

    DMARC

    How to fix

    Add rua=mailto:you@example.com to the record to receive daily aggregate reports from receivers.

Healthy (3)

  • 1 MX record found.

    MX
  • SPF record is valid, using 5 of 10 DNS lookups.

    SPF
  • DKIM selector k2 has a healthy RSA key.

    DKIM

    k2 (k2._domainkey.golevo.com)

Evidence

MX

1 record
  • golevo-com.mail.protection.outlook.compriority 0

SPF

5 of 10 lookups
DNS lookups5 / 10
golevo.com
include:spf.protection.outlook.com
include:_spf-include.iamemonline.com
include:_spf1.iamemonline_com._d.easydmarc.pro

Root TXT

5 records
  • 9NLIAL4V6IL6IUUPGP2H226QUA
  • google-site-verification=304sY9z5egwM3s1eCt77gLOJq2s5UPgCu-dx2b5eIqM
  • mscid=CdXqC9L7V6saKmxLIGroFywgmpimqU28o6WAsXJqipaQNCHHXajTXQ+DU8lhv/il4aliWArXI5n2HRz/37px9Q==
  • sem9bh9fvp1jukq3o6hcbia4q4
  • v=spf1 include:spf.protection.outlook.com include:_spf-include.iamemonline.com -all

DKIM selectors

2 records
  • selector1selector1._domainkey.golevo.com
    CNAME selector1-golevo-com._domainkey.golevo.onmicrosoft.com
    • v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDNQTbGOwSmzwi25EouixX5JxPCsquFQxBdq4udqkDqH9t0R1E67iVIzAXPEWHksIgGYYUAj6/Zs6TTM/Q/NEJAIk/8vZKor5QrFWbgQzapUGMynVsIsxc/yoOqWmIaxmdWW4br+Vy4nj7GxnpPeIG/S2GGfof4KAqlXhY963UxowIDAQAB; n=1024,1456524787,1472249587
  • selector2selector2._domainkey.golevo.com
    CNAME selector2-golevo-com._domainkey.golevo.onmicrosoft.com

    No TXT records returned for this selector.

  • k2k2._domainkey.golevo.com
    CNAME dkim2.mcsv.net
    • v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;

Probed with no records: google, 20230601, 20210112, k1, s1, s2, default, dkim, mail

DMARC

1 record
v=DMARC1; p=none;
v=DMARC1
Identifies this TXT record as a DMARC policy. Must be the first tag.
p=none
Monitoring only: receivers deliver failing mail normally and just send reports.
sp=nonedefault
No sp= tag is published, so subdomains inherit the domain's p= policy.
pct=100default
No pct= tag is published, so the policy applies to all failing mail.
adkim=rdefault
No adkim= tag is published, so DKIM alignment is relaxed: any subdomain of the From domain may sign.
aspf=rdefault
No aspf= tag is published, so SPF alignment is relaxed: the envelope sender may be any subdomain of the From domain.
Raw JSON