Dataweaz

bfp.gov.ph

Summary

Registrar
—
Status
Created on
—
Expires on
—
Name servers
newscott.gov.ph, ns3.dns.gov.ph, ns4.dns.gov.ph, ns5.dns.gov.ph
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
SPF
Soft
DKIM
No key found among the common selectors
Website
See the website

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for bfp.gov.ph.

RuleValueResult
include_spf.google.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:_spf.google.com ~all

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 bfp.gov.ph arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from bfp.gov.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 @bfp.gov.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

bfp.gov.ph  MX  10 mx1.bfp.gov.ph.
bfp.gov.ph  MX  20 mx2.bfp.gov.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.bfp.gov.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

bfp.gov.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.bfp.gov.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.bfp.gov.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.bfp.gov.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.bfp.gov.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 bfp.gov.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
A172.64.145.157
A104.18.42.99

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
newscott.gov.ph52.139.253.232
ns3.dns.gov.ph202.90.153.37
ns4.dns.gov.ph202.90.153.36
ns5.dns.gov.ph20.6.90.190

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @bfp.gov.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.com74.125.71.26
5alt2.aspmx.l.google.com142.251.127.26
5alt1.aspmx.l.google.com192.178.213.27
10aspmx2.googlemail.com192.178.213.27
10aspmx3.googlemail.com142.251.127.26

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.bfp.gov.ph.

NameContent
bfp.gov.ph1srdb6omcss9uol7cam8qaqfbp
bfp.gov.ph17jffnrnobumbmfqdstgclr3hb
bfp.gov.ph7a25un1ip7aad2b8o3q7cg613d
bfp.gov.phcerpk2ds8tqkedq4fhs3hdhfmc
bfp.gov.ph5ad62s9hvm2q41gptfpj7tn31s
bfp.gov.phgck0c9fbmf6t5ruvkss9u2vhi4
bfp.gov.ph80fhimsf7060hgtbgg3d6kv2gp
bfp.gov.phtrq9n23h509ywyytbyszw3jj6b1y8bmx
bfp.gov.phk20qwrdl9qvdynt8fzks7rwgr332swkx
bfp.gov.phh9xhkyrd0nq6hcdy1ykh7v4msznwhn1z
bfp.gov.phcjtqne0ror3eonf9ltk3g9i5bq
bfp.gov.phv=spf1 include:_spf.google.com ~all
bfp.gov.phhs4qh4ds5e2ahqdq1i1ghgplt3
bfp.gov.ph8dnko3nnng93i43ehh3oiqe2vh
bfp.gov.phhkf2c5ttqndgn0qc8a904rhi95
bfp.gov.phcoc767ap8q4havhbllnf0q8fo8
bfp.gov.ph6c68rvtc8gsu32cjdglijk4v6q
bfp.gov.phf9ltkhh9ktrbc6mug9n655look
bfp.gov.ph24mint8r414bmim0rp0ol7c4o5
bfp.gov.phq79iakoslochojdbalo3hue374
bfp.gov.phkp9oer0cqdcrclnsmj86kuhd42
bfp.gov.phtl3oeugij4lqrev6ejk0cvc73g
bfp.gov.ph47os6orvv9hqepdpjqrbbjtsed
bfp.gov.ph_mpk9klro69upkzphl7t7xrb7kfi198s
bfp.gov.pho0c4t9gr1mjeqquqqnjn3albnc
bfp.gov.ph_rymwz0k301kmq43eza390xpokdqgp0t
bfp.gov.phpfb0j7846m6hdcqs85igg8h4jr
bfp.gov.phdgbl6djj4mn123cjhnjpfmnoo4
bfp.gov.phr419d2pu7e1bdjrneg2ngedvmp
bfp.gov.ph3ssdcjco95q9uc46oo5p68bt60
bfp.gov.phs3bq8bvcf1jn8cevo64dgd2c4l
bfp.gov.phlf495ncnlg8brlnrud89t7s831
bfp.gov.phguk8fd2c13581ajudc7d1q91m7
bfp.gov.phjvbs0dbcahajk3gl19esi6gd60
bfp.gov.phmg0rjg0f9r488ut517n2isv869
bfp.gov.phgoogle-site-verification=qUT2QzPZbdxAfgMWhTCRFQgpugAKzmJGdIG13ARUJuw
bfp.gov.ph_dr6bx7pq595rvsn8ducxi9ym9cm8ho3
bfp.gov.ph_gun3zfydu61on4lglhfi0pzvfhhals2
bfp.gov.phqqdrm93x894qcvw7t8v1v8n07gxc12b9
bfp.gov.ph_q90ide16ngndg9asap1ieb9xdrjl662
bfp.gov.ph69dlerd304p0ar1c7ejqo1e1h6
bfp.gov.phkf639c2ilskf2kmj91dteft29v
bfp.gov.ph_up62jdl2jllhrcpj7as1njnu37vyuai
bfp.gov.phlak3t1pk96c447gqppfbch32aj
bfp.gov.phnbmt2cw56svsytq27fnrt58r48392fy5
bfp.gov.phonq3ckh09oa7blt8alp3otbvkt
bfp.gov.ph5m8gf9a3cq0o2krl5257duki6k
bfp.gov.phh9knljm51531t6im8hvm6v13hn
bfp.gov.ph_38bla7rn64w6u60h4hn68gt62ed5sst
bfp.gov.ph_4i1tvhu95116ogurbivu4qh0la4jboi
bfp.gov.phbqsh0tsec0jrm82dbnftlkoq7u
bfp.gov.phkbq76pjpf8ifsfhbqst2pdvree
bfp.gov.ph_kr5h42p2exf1dtk9naoefgp71a6vjow
bfp.gov.phrp8vb49s529uqks43t28670m4c

Related IP addresses

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

IP addressUsed for/24 block
172.64.145.157Website172.64.145.0/24
104.18.42.99Website104.18.42.0/24
52.139.253.232Name server newscott.gov.ph52.139.253.0/24
202.90.153.37Name server ns3.dns.gov.ph202.90.153.0/24
202.90.153.36Name server ns4.dns.gov.ph202.90.153.0/24
20.6.90.190Name server ns5.dns.gov.ph20.6.90.0/24
74.125.71.26Mail server aspmx.l.google.com74.125.71.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com, Mail server aspmx3.googlemail.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com, Mail server aspmx2.googlemail.com192.178.213.0/24

WHOIS of the domain bfp.gov.ph