Dataweaz

hardwarezone.com.sg

Summary

Registrar
CSC Corporate Domains Inc
Status
clientTransferProhibited
Created on
March 17, 1999
Expires on
March 16, 2027
Name servers
ns-1773.awsdns-29.co.uk, ns-370.awsdns-46.com, ns-533.awsdns-02.net, ns-1531.awsdns-63.org
Mail servers
aspmx.l.google.com, inbound-smtp.us-west-2.amazonaws.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx4.googlemail.com, aspmx3.googlemail.com, aspmx2.googlemail.com, aspmx5.googlemail.com
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

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

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

Record

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;

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

hardwarezone.com.sg  MX  10 mx1.hardwarezone.com.sg.
hardwarezone.com.sg  MX  20 mx2.hardwarezone.com.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.hardwarezone.com.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

hardwarezone.com.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.hardwarezone.com.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.hardwarezone.com.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.hardwarezone.com.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.hardwarezone.com.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 hardwarezone.com.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.

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
ns-1773.awsdns-29.co.uk205.251.198.237
ns-370.awsdns-46.com205.251.193.114
ns-533.awsdns-02.net205.251.194.21
ns-1531.awsdns-63.org205.251.197.251

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @hardwarezone.com.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
5aspmx.l.google.com64.233.167.27
10inbound-smtp.us-west-2.amazonaws.com35.161.157.106
10alt2.aspmx.l.google.com142.251.127.26
10alt1.aspmx.l.google.com192.178.213.26
20aspmx4.googlemail.com172.253.148.27
20aspmx3.googlemail.com142.251.127.26
20aspmx2.googlemail.com192.178.213.27
20aspmx5.googlemail.com142.250.147.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.hardwarezone.com.sg.

NameContent
hardwarezone.com.sgu1q9ens77bqvca84nmph28saog
hardwarezone.com.sg3dny5qqcjmpmj15ffn4wv2qfrcg28p9q
hardwarezone.com.sgjbmmxlrkmfmbh1b7p8z9ws50smnbnznp
hardwarezone.com.sggoogle-site-verification=KSIYzS8S4Sf2DoqxjOI9ZAWHF-lP4sndmKPnbSSXWg8
hardwarezone.com.sgzh9kn065tdkbn1k2fgsvw7dvfqmlwrx8
hardwarezone.com.sgzlb22wkdwfrhh8w3j41622bkp78qssrb
hardwarezone.com.sgsv26ipsn6qsh65a0fsifnmq3cf
hardwarezone.com.sgdfqvr60i436bj3vspslon902o8
hardwarezone.com.sg8w3ygjt8xrrjw6k2zbfj07znm66cwy8m
_dmarc.hardwarezone.com.sgv=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1;

Related IP addresses

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

IP addressUsed for/24 block
13.249.228.99Website13.249.228.0/24
13.249.228.19Website13.249.228.0/24
13.249.228.34Website13.249.228.0/24
13.249.228.48Website13.249.228.0/24
205.251.198.237Name server ns-1773.awsdns-29.co.uk205.251.198.0/24
205.251.193.114Name server ns-370.awsdns-46.com205.251.193.0/24
205.251.194.21Name server ns-533.awsdns-02.net205.251.194.0/24
205.251.197.251Name server ns-1531.awsdns-63.org205.251.197.0/24
64.233.167.27Mail server aspmx.l.google.com64.233.167.0/24
35.161.157.106Mail server inbound-smtp.us-west-2.amazonaws.com35.161.157.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com, Mail server aspmx3.googlemail.com142.251.127.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.27Mail server aspmx4.googlemail.com172.253.148.0/24
192.178.213.27Mail server aspmx2.googlemail.com192.178.213.0/24
142.250.147.27Mail server aspmx5.googlemail.com142.250.147.0/24

WHOIS of the domain hardwarezone.com.sg

Domain Name: hardwarezone.com.sg
Unicode Name: hardwarezone.com.sg
Updated Date: 2026-03-09T05:05:37Z
Creation Date: 1999-03-17T09:21:06Z
Registry Expiry Date: 2027-03-16T16:00:00Z
Registrar: CSC Corporate Domains Inc
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
VerifiedID Status: VerifiedID@SG-OK
Registry Lock:
Registrant Name: SPH MEDIA LIMITED
Admin Name: SPH MEDIA LIMITED
Tech Name: SPH MEDIA LIMITED
Tech Email: [email protected]
Name Server: ns-1531.awsdns-63.org
Name Server: ns-1773.awsdns-29.co.uk
Name Server: ns-370.awsdns-46.com
Name Server: ns-533.awsdns-02.net
DNSSEC: unsigned
>>> Last update of WHOIS database: 2026-10-02T23:41:23Z <<<

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: 542 msec
% WHEN: Fri Oct 02 23:41:23 UTC 2026