Dataweaz

sunlife.com.ph

Summary

Registrar
—
Status
Created on
—
Expires on
—
Name servers
a6-64.akam.net, a1-225.akam.net, a14-66.akam.net, a7-65.akam.net, a8-66.akam.net, a5-67.akam.net
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from sunlife.com.ph but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1;p=reject;rua=mailto:[email protected];

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for sunlife.com.ph.

RuleValueResult
include_spf.salesforce.comAllowed
includemktomail.comAllowed
includespf.protection.outlook.comAllowed
include_spf.fireeyecloud.comAllowed
ip4159.208.32.74Allowed
ip4159.208.32.75Allowed
ip4159.208.34.171Allowed
ip4159.208.34.172Allowed
include_spf.google.comAllowed
all—Rejected

Top-level DNS lookups: 5 of 10 allowed

Record

v=spf1 include:_spf.salesforce.com include:mktomail.com include:spf.protection.outlook.com include:_spf.fireeyecloud.com ip4:159.208.32.74 ip4:159.208.32.75 ip4:159.208.34.171 ip4:159.208.34.172 include:_spf.google.com -all

E-mail signing (DKIM)

DKIM keys published by sunlife.com.ph under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
selector1Microsoft 365RSA 2048 bitsActive
selector2Microsoft 365RSA 2048 bitsActive

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to sunlife.com.ph arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from sunlife.com.ph was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @sunlife.com.ph address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

sunlife.com.ph  MX  10 mx1.sunlife.com.ph.
sunlife.com.ph  MX  20 mx2.sunlife.com.ph.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.sunlife.com.ph.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

sunlife.com.ph  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.sunlife.com.ph, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.sunlife.com.ph  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.sunlife.com.ph, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.sunlife.com.ph  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of sunlife.com.ph

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A104.85.50.106

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
a6-64.akam.net23.211.133.64
a1-225.akam.net193.108.91.225
a14-66.akam.net184.26.161.66
a7-65.akam.net23.61.199.65
a8-66.akam.net2.16.40.66
a5-67.akam.net95.100.168.67

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @sunlife.com.ph addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
1aspmx.l.google.com66.102.1.26
5alt2.aspmx.l.google.com142.251.127.27
5alt1.aspmx.l.google.com192.178.213.27
10alt4.aspmx.l.google.com142.250.147.26
10alt3.aspmx.l.google.com172.253.148.27

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.sunlife.com.ph.

NameContent
sunlife.com.phZOOM_verify_0mubr9gLQbidw15cT2cTNw
sunlife.com.phgoogle-site-verification=QM5ze1KZ1TaqoPl5JhTk7ArHNBRXHPIOOFwqGsmJC9M
sunlife.com.ph61x5g1t3zzgg962m288tcc5m294jtqrz
sunlife.com.phgoogle-site-verification=-D7-5RbOnuJz1EyPP-sBsVjNmS4uHTyxFzDJnhxynKM
sunlife.com.phMS=ms46755188
sunlife.com.ph_k0vo71oi6l5ph3toygpq1mub01342sn
sunlife.com.php3y3zr8w90vy9f6bwdbmzcgt01xp7jl7
sunlife.com.phgoogle-site-verification=V8uJoKVAyVp9J3HkyS_ya3oB_QntHIkBU8xIwBJZ__Y
sunlife.com.ph_0y73tsbepxz86w1653aibtub9cqjoaa
sunlife.com.phccbx6ph1r0rv5g9pfnfh7c1y8f8w30lq
sunlife.com.phv=spf1 include:_spf.salesforce.com include:mktomail.com include:spf.protection.outlook.com include:_spf.fireeyecloud.com ip4:159.208.32.74 ip4:159.208.32.75 ip4:159.208.34.171 ip4:159.208.34.172 include:_spf.google.com -all
sunlife.com.phr84rddy22hqcqz31hcf5nr8vd9zmdy3r
sunlife.com.phpg6s1zhzfjnjss377vyh9rb5rp4tqdzr
sunlife.com.phf005fdca3a224983928ef53186c44033
sunlife.com.ph_4onjk0q5fq40n8neeoqexxbr1avlyr3
_dmarc.sunlife.com.phv=DMARC1;p=reject;rua=mailto:[email protected];
google._domainkey.sunlife.com.phv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApMC6K0RkAzI/J/nTZKGRsWoRDgB7Ve5IxJYJwN1xjWs0XzASJr2T4mP2d05KYly0aR96I2OAELWL0Ym53cTw94yByPCshW1dDlMbY+gtu8wQ3l6hqDupCKrKQa2nCVKIoLNgjcCCBuVHsvG/YhXU8gLfZFXm5YrHXfWwX+jgkkTaC4XlZla40QNEi6/dYx7UWgnB/D2IJah8oucDG0EtKBu9brBw2cPVK/Zk+NXxTL20E5UfRYQXKQDarD5SaGsMRLVqI4wX9U1DNTH+PJc/NpVtydwzKF/KX/L8k1BuEx0VuJ/1TB2Fx3xwEnXLr+GY78jjj0noPiA6L96s6IRmBwIDAQAB
selector1._domainkey.sunlife.com.phv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3O8Cl+JgaxNSA9ioIZlNjhC+ge301h4n7k7UdJC/QbzlAMKIvFq2/I1+OZAB/akFO6OklqM5LcT1LtbE7KUhapPC0PHLOFZrawf3bO7dOEMBe0mW+oqi+u7j5Sxi+z0rPXfFhvXUaOGgED4OCwz/Und2IxvZ1dijpXt6eqmitmD2PK1e7zH5Na9EEeWJlMkm4P2f8OL12BImx4OF0MPuaD8IlhzTqTGguD8ceD+Q0VXSIfwiQ83pi4O6dF4p8mfK4mpTQuobWewtk5NDtCUhjnR+w6oWzwHii+GS2j8EowghPC16iUJaspv28WjKMczQwwAr/oxR5ONViM2/5yr5CQIDAQAB;
selector2._domainkey.sunlife.com.phv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArUFTEOP/Iv/S0W6dXCRbI/SFLpWwsSfeRVsKVYg+dGBiFPAgU7JSu2t5tvo0N+BRTk0dVZMJ/i/HXGYFbLGaVCN+FYhsLjBu/ToXX122Das4WfSOt73/DO4t//M2non/IaU6cn1GPuxDap4gjYCCZ+fmoQeaznMqTlvrIlmBEZGJ0EmCQeLARoycSBXSgRWJJEuVbojfUmsjclkXm0b8hCCG7NyIN2ZAHgSfF11Jbln1jpJELxYL7YjbSemV+GrmUwejjsSOB4S8aa0ruwX2tBRd0apROrLsbHSYNRTGyjNTWHAsni1VJEGIkbBqD5luU7Tu+qqhNPomAVP5pk2f4QIDAQAB;

Related IP addresses

IPv4 addresses used by sunlife.com.ph: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
104.85.50.106Website104.85.50.0/24
23.211.133.64Name server a6-64.akam.net23.211.133.0/24
193.108.91.225Name server a1-225.akam.net193.108.91.0/24
184.26.161.66Name server a14-66.akam.net184.26.161.0/24
23.61.199.65Name server a7-65.akam.net23.61.199.0/24
2.16.40.66Name server a8-66.akam.net2.16.40.0/24
95.100.168.67Name server a5-67.akam.net95.100.168.0/24
66.102.1.26Mail server aspmx.l.google.com66.102.1.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
142.250.147.26Mail server alt4.aspmx.l.google.com142.250.147.0/24
172.253.148.27Mail server alt3.aspmx.l.google.com172.253.148.0/24
159.208.32.74Authorized by SPF159.208.32.0/24
159.208.32.75Authorized by SPF159.208.32.0/24
159.208.34.171Authorized by SPF159.208.34.0/24
159.208.34.172Authorized by SPF159.208.34.0/24

WHOIS of the domain sunlife.com.ph