Summary
- Registrar
- —
- Status
- Active
- Created on
- June 25, 2015
- Expires on
- July 6, 2027
- Name servers
- ns4.xtom.com, ns1.xtom.com, ns2.xtom.com, ns3.xtom.com
- Mail servers
- in1-smtp.messagingengine.com, in2-smtp.messagingengine.com
- SPF
- Neutral
- DKIM
- 3 keys found
- Website
- See the website
Authorized senders (SPF)
The record gives no instruction for other servers.
SPF lists the servers allowed to send e-mails for xtom.com.hk.
| Rule | Value | Result |
|---|---|---|
| include | spf.messagingengine.com | Allowed |
| all | — | Neutral |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 include:spf.messagingengine.com ?all
E-mail signing (DKIM)
DKIM keys published by xtom.com.hk under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| fm1 | Fastmail | RSA 2048 bits | Active |
| fm2 | Fastmail | RSA | Revoked |
| fm3 | Fastmail | RSA | Revoked |
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 xtom.com.hk arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from xtom.com.hk 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 @xtom.com.hk 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
xtom.com.hk MX 10 mx1.xtom.com.hk. xtom.com.hk MX 20 mx2.xtom.com.hk.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.xtom.com.hk.
- 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
xtom.com.hk 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.xtom.com.hk, 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.xtom.com.hk 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.xtom.com.hk, 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.xtom.com.hk 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 xtom.com.hk
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.
| Type | IP address |
|---|---|
| A | 45.125.0.3 |
| AAAA | 2403:2c80::3 |
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.
| Server | IP address |
|---|---|
| ns4.xtom.com | 188.244.99.134 |
| ns1.xtom.com | 188.244.98.133 |
| ns2.xtom.com | 188.244.99.133 |
| ns3.xtom.com | 188.244.98.134 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @xtom.com.hk 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.
| Priority | Server | IP address |
|---|---|---|
| 10 | in1-smtp.messagingengine.com | 103.168.172.217 |
| 20 | in2-smtp.messagingengine.com | 202.12.124.217 |
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.xtom.com.hk.
| Name | Content |
|---|---|
| xtom.com.hk | v=spf1 include:spf.messagingengine.com ?all |
| fm1._domainkey.xtom.com.hk | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArQAQxHcUlvCkgZk15aH+O8z4qHdOz3XeMPeir4zvIaU+d2WgxBq4CRjDPcWtcRARqzez29ge8wO05I56jko75GrEI92WQIibbVSYlkrMEYCud54905BwgP/bhmcCzxooqfr6tZpJyANV0udYwvPz8/dyI5tqUBcZj5chP8vjkDibP7C8j1Sc4h3F48nJ1583oT7QG/P8oo7QXnkTXhpm4PZ5wyBy0/6JRAJDE/rZGZleaT151yOla1iLr5eK5GaDWTaDkK/GwScaOlUPwK0lfpJie8ckv0vRhn2eEkairtKXO2PR7uAad97vS6HdJsR6EvyjSzemBQ1RPYD/sm2ZcQIDAQAB |
| fm2._domainkey.xtom.com.hk | v=DKIM1; k=rsa; n=Intentionally_Left_Blank_As_Per_DKIM_Rotation_BCP; p= |
| fm3._domainkey.xtom.com.hk | v=DKIM1; k=rsa; n=Intentionally_Left_Blank_As_Per_DKIM_Rotation_BCP; p= |
Related IP addresses
IPv4 addresses used by xtom.com.hk: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 45.125.0.3 | Website | 45.125.0.0/24 |
| 188.244.99.134 | Name server ns4.xtom.com | 188.244.99.0/24 |
| 188.244.98.133 | Name server ns1.xtom.com | 188.244.98.0/24 |
| 188.244.99.133 | Name server ns2.xtom.com | 188.244.99.0/24 |
| 188.244.98.134 | Name server ns3.xtom.com | 188.244.98.0/24 |
| 103.168.172.217 | Mail server in1-smtp.messagingengine.com | 103.168.172.0/24 |
| 202.12.124.217 | Mail server in2-smtp.messagingengine.com | 202.12.124.0/24 |
WHOIS of the domain xtom.com.hk
---------------------------------------------------------------------- Whois server by HKIRC ---------------------------------------------------------------------- .hk top level Domain names can be registered via HKIRC-Accredited Registrars. Go to https://www.hkirc.hk/content.jsp?id=280 for details. ---------------------------------------------------------------------- Domain Name Information: Domain Name: XTOM.COM.HK Contract Version: Refer to registrar Domain Name Commencement Date: 25-06-2015 Expiry Date: 06-07-2027 Re-registration Status: Complete Domain Status: Active DNSSEC: signedDelegation Registrar Name: Netim Registrar Contact Information: Email: [email protected] Reseller: CDN Variant / Punycode Registrant Contact Information: Company English Name (It should be the same as the registered/corporation name on your Business Register Certificate or relevant documents): XTOM HONG KONG LIMITED Company Chinese name: Country: Hong Kong (HK) Email: Redacted for Privacy Purposes Name Servers Information: NS1.XTOM.COM NS2.XTOM.COM NS3.XTOM.COM NS4.XTOM.COM Status Information: Domain Prohibit Status: If you have any doubt on the Registrant Contact Information, please feel free to contact the relevant registrar for details. Please accept and agree that the registrar may pass your contact information to the relevant domain contact therefore the domain contact can decide how they will follow. ------------------------------------------------------------------------------- The Registry contains ONLY .com.hk, .net.hk, .edu.hk, .org.hk, .gov.hk, idv.hk. and .hk $domains. ------------------------------------------------------------------------------- WHOIS Terms of Use By using this WHOIS search enquiry service you agree to these terms of use. The data in HKDNR's WHOIS search engine is for informational purposes only and HKDNR does not guarantee the accuracy of the data. The data is provided to assist people obtaining information about the registration record of domain names registered by HKDNR. You agree to use the data for lawful purposes only. In light of the General Data Protection Regulation, HKIRC reserves the right to not make available certain data on this WHOIS search enquiry. You are not authorised to use high-volume, electronic or automated processes to access, query or harvest data from this WHOIS search enquiry service. You agree that you will not and will not allow anyone else to: a. use the data for mass unsolicited commercial advertising of any sort via any media including telephone, email or fax; or b. enable high volume, automated or electronic processes that apply to HKDNR or its computer systems including the WHOIS search enquiry service; or c. without the prior written consent of HKDNR compile, repackage, disseminate, disclose to any third party or use the data for a purpose other than obtaining information about a domain name registration record; or d. use such data to derive an economic benefit for yourself. HKIRC in its sole discretion may terminate your access to the WHOIS search enquiry service (including but not limited to blocking your IP address) at any time due to, including but not limited to, excessive use of the WHOIS search enquiry service. HKDNR may modify these terms of use at any time by publishing the modified terms of use on its website. % Query time: 998 msec % WHEN: Thu Oct 01 18:39:14 UTC 2026