Dataweaz

pcf.org.sg

Summary

Registrar
Singnet Pte Ltd
Status
ok
Created on
July 31, 2000
Expires on
July 30, 2027
Name servers
dnssec1.singnet.com.sg, dnssec3.singnet.com.sg, dnssec2.singnet.com.sg
Mail servers
pcf-org-sg.mail.protection.outlook.com
SPF
Soft

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 pcf.org.sg.

RuleValueResult
mx—Allowed
ip4203.126.43.55Allowed
ip4103.11.190.103Allowed
ip420.44.239.146Allowed
ip4168.63.237.59Allowed
ip4103.250.59.14Allowed
ip4129.126.97.50Allowed
includespf.protection.outlook.comAllowed
include_spf.salesforce.comAllowed
includemailgun.orgAllowed
all—Suspicious

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 mx ip4:203.126.43.55 ip4:103.11.190.103 ip4:20.44.239.146 ip4:168.63.237.59 ip4:103.250.59.14 ip4:129.126.97.50 include:spf.protection.outlook.com include:_spf.salesforce.com include:mailgun.org ~all

E-mail signing (DKIM)

DKIM keys published by pcf.org.sg under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
smtp—RSA 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 pcf.org.sg arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from pcf.org.sg 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 @pcf.org.sg 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

pcf.org.sg  MX  10 mx1.pcf.org.sg.
pcf.org.sg  MX  20 mx2.pcf.org.sg.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.pcf.org.sg.
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

pcf.org.sg  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.pcf.org.sg, 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.pcf.org.sg  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.pcf.org.sg, 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.pcf.org.sg  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 pcf.org.sg

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
A162.159.134.42

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
dnssec1.singnet.com.sg165.21.83.11
dnssec3.singnet.com.sg165.21.100.11
dnssec2.singnet.com.sg165.21.100.11

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @pcf.org.sg 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
10pcf-org-sg.mail.protection.outlook.com52.101.137.2

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.pcf.org.sg.

NameContent
pcf.org.sgfacebook-domain-verification=21i4v2bi5ivrdp4mess6ds92flhywc
pcf.org.sg8vvj9rmr7l3suqv7qmub2agpev
pcf.org.sgMS=ms98734684
pcf.org.sghp5226kg3yk59q21lpcv6rjhqdtglnm6
pcf.org.sggoogle-site-verification=Xui1u4WqSDhZxoRYgaTZWmUgHwkC5pzpsVGN2XG5swI
pcf.org.sgamazonses:Q3hQq3pT+V2VSyzMVZpe5588iXboZAsXE7c2l1NgKTk=
pcf.org.sgv=spf1 mx ip4:203.126.43.55 ip4:103.11.190.103 ip4:20.44.239.146 ip4:168.63.237.59 ip4:103.250.59.14 ip4:129.126.97.50 include:spf.protection.outlook.com include:_spf.salesforce.com include:mailgun.org ~all
pcf.org.sg_or0qsigk0wmwdarl9abnu747uw5ogwc
pcf.org.sg18sk0vg9mig3gfodknmpiuar80
pcf.org.sgukdpedek2kqk713e81d2hhgftt
smtp._domainkey.pcf.org.sgk=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoFg3BbOekyy+atXp1n3EZAv0D+tBOKM8eed27wq7sOTHRJGP8E79qCxSJNA/HRItPtNoY7sMESthgFw9znnk0P4565vJtqSaCKJZ4/uyyqhJp8kxoFNI7jfdvJ+5v7UiVLFY72/fuS8WBNST+SQcFK/PWZDFBAXY8YB757mF9L+ixroWdFyexcz8Qzb5ab3kTcfAnQSodWk916ckYPNMWHTndBhfXTybfx7dofFb+BhMFgFnwIo8HXORcWiT9kdBLeAagapS7OlhJ3pDue9uWKtwjEwH4xzbCqyKivuNAJVdjmsKhJgNNBDzbk6iIc6I32OWbE39MQf4b+bRcsSSOQIDAQAB

Related IP addresses

IPv4 addresses used by pcf.org.sg: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
162.159.134.42Website162.159.134.0/24
165.21.83.11Name server dnssec1.singnet.com.sg165.21.83.0/24
165.21.100.11Name server dnssec3.singnet.com.sg, Name server dnssec2.singnet.com.sg165.21.100.0/24
52.101.137.2Mail server pcf-org-sg.mail.protection.outlook.com52.101.137.0/24
203.126.43.55Authorized by SPF203.126.43.0/24
103.11.190.103Authorized by SPF103.11.190.0/24
20.44.239.146Authorized by SPF20.44.239.0/24
168.63.237.59Authorized by SPF168.63.237.0/24
103.250.59.14Authorized by SPF103.250.59.0/24
129.126.97.50Authorized by SPF129.126.97.0/24

WHOIS of the domain pcf.org.sg

Domain Name: pcf.org.sg
Unicode Name: pcf.org.sg
Updated Date: 2026-08-29T16:04:05Z
Creation Date: 2000-07-31T04:17:59Z
Registry Expiry Date: 2027-07-30T16:00:00Z
Registrar: Singnet Pte Ltd
Domain Status: ok https://icann.org/epp#ok
VerifiedID Status: VerifiedID@SG-Not Required
Registry Lock:
Registrant Name: PAP COMMUNITY FOUNDATION
Admin Name: PAP COMMUNITY FOUNDATION
Tech Name: PAP COMMUNITY FOUNDATION
Tech Email: [email protected]
Name Server: dnssec1.singnet.com.sg
Name Server: dnssec2.singnet.com.sg
Name Server: dnssec3.singnet.com.sg
DNSSEC: unsigned
>>> Last update of WHOIS database: 2026-10-02T19:19:19Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

% ----------------------------------------------------------------------
% SGNIC WHOIS Server
% ----------------------------------------------------------------------
%
% This data is provided for information purposes only.

% Query time: 689 msec
% WHEN: Fri Oct 02 19:19:19 UTC 2026