Dataweaz

headfirst.cloud

Summary

Registrar
PDR Ltd.
Status
clientTransferProhibited
Created on
November 22, 2023
Expires on
November 22, 2026
Name servers
ns4.headfirst.cloud, ns2.headfirst.cloud, ns3.headfirst.cloud, ns1.headfirst.cloud
Mail servers
mail.headfirst.cloud
DMARC
Reject
SPF
Strict
DKIM
2 keys found
Website
See the website

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 headfirst.cloud but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Strict
SPF alignment
Strict
Aggregate reports
[email protected], dmarc-tkn_38c3ecb9bf9e0565a9b8973a77f30193@mailsrv1.captaindns.com
Failure reports
[email protected]

Record

v=DMARC1; p=reject; sp=reject; np=reject; adkim=s; aspf=s; rua=mailto:[email protected],mailto:dmarc-tkn_38c3ecb9bf9e0565a9b8973a77f30193@mailsrv1.captaindns.com; ruf=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 headfirst.cloud.

RuleValueResult
a—Allowed
mx—Allowed
all—Rejected

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 a mx -all

E-mail signing (DKIM)

DKIM keys published by headfirst.cloud under the most common selectors. Other keys may exist under selectors specific to each sending service.

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

headfirst.cloud  MX  10 mx1.headfirst.cloud.
headfirst.cloud  MX  20 mx2.headfirst.cloud.

What the record contains

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

headfirst.cloud  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.headfirst.cloud, 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.headfirst.cloud  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.headfirst.cloud, 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.headfirst.cloud  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 headfirst.cloud

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.

No IP address: the domain does not point to any web server.

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
ns4.headfirst.cloud185.136.99.7
ns2.headfirst.cloud185.136.97.7
ns3.headfirst.cloud185.136.98.7
ns1.headfirst.cloud185.136.96.7

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @headfirst.cloud 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
10mail.headfirst.cloud46.225.196.94

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.headfirst.cloud.

NameContent
headfirst.cloudv=spf1 a mx -all
_dmarc.headfirst.cloudv=DMARC1; p=reject; sp=reject; np=reject; adkim=s; aspf=s; rua=mailto:[email protected],mailto:dmarc-tkn_38c3ecb9bf9e0565a9b8973a77f30193@mailsrv1.captaindns.com; ruf=mailto:[email protected]
selector1._domainkey.headfirst.cloudv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4IWSMd9ui8QUzxfQfjxsJJ6lvO1kJ331qWgubi1VGJzjF+DSHfXWYdIMRNcUJabYGhUdL1wTu7oZIlx38RDPjG5NeuVig3t/nb9aE5vLYjQMNf2kBfe5Y8x6YsTedMTPDcJ4719QopV5WGpJ+bu0acDaiPpBtbV4cy21yIiUBoOobK16fAS3jYgyrRa5+VsHiPQwyclHBDiIFfVJuZ0lgXT9aQU95xXBREZuiPt/o7L7dXup05wzYS6AyS3+R/L/czHJiv5vKENbfcUcthmX6gcEzviDH/6rRxh+n61FiJJ0QHdg8fvPE5+j3ZwQNMipj4FYOc7Te1W3JNbOR5sKZwIDAQAB
selector2._domainkey.headfirst.cloudv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzTeVGtlQbDVcZSMyz0O0v5ZNyebzVLwKYC1PDG8vBxoaxcI+Pn4ONeir7vvP87cOxSQJREh6i3MamCwou ikMdzqldsIpvDYogwgW9CZXqBobeE9pnFT0BYUmkjRcJqCQ0lGiWOq34MtqXTy0706jJUFoVIT5cZUNEnx7gahUOBolXK6EyQRCcqmfWApfHLI2oqLWHvV5uSJKqbmp20b8wzcRQc6QkzeP GfBo/W79aRTQlYYd/NcjYXBQEkjmc1LC0+2M0q9G4o8AFCyuGln5Ls6mu4BpNBSiaALG7h4dzp0BWkStgMBynb6C5YI++mvz6EUHue5KNt2Mqt13HFxpLwIDAQAB

Related IP addresses

IPv4 addresses used by headfirst.cloud: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
185.136.99.7Name server ns4.headfirst.cloud185.136.99.0/24
185.136.97.7Name server ns2.headfirst.cloud185.136.97.0/24
185.136.98.7Name server ns3.headfirst.cloud185.136.98.0/24
185.136.96.7Name server ns1.headfirst.cloud185.136.96.0/24
46.225.196.94Mail server mail.headfirst.cloud46.225.196.0/24

WHOIS of the domain headfirst.cloud

Domain Name: headfirst.cloud
Registry Domain ID: DO_7f63e1ab7a4a77342777d19b45bf1899-ARUBA
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2026-07-15T14:49:40.888Z
Creation Date: 2023-11-22T21:52:06.728Z
Registry Expiry Date: 2026-11-22T21:52:06.728Z
Registrar: PDR Ltd.
Registrar IANA ID: 303
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +971.72046060
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns1.headfirst.cloud
Name Server: ns2.headfirst.cloud
Name Server: ns3.headfirst.cloud
Name Server: ns4.headfirst.cloud
DNSSEC: signedDelegation
URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

>>> Last update of WHOIS database: 2026-10-01T10:46:59.269Z <<<

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

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Tucows Registry for informational
purposes only, and it does not guarantee its accuracy. Tucows Registry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Tucows Registry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass  unsolicited, commercial advertising
or solicitations to entities other than your existing  customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Tucows Registry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.
Domain Name: HEADFIRST.CLOUD
Registry Domain ID: DO_7f63e1ab7a4a77342777d19b45bf1899-ARUBA
Registrar WHOIS Server: whois.publicdomainregistry.com
Registrar URL: www.publicdomainregistry.com
Updated Date: 2026-07-15T14:49:41Z
Creation Date: 2023-11-22T21:52:06Z
Registrar Registration Expiration Date: 2026-11-22T21:52:06Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: GDPR Masked
Registrant Name: GDPR Masked
Registrant Organization: GDPR Masked
Registrant Street: GDPR Masked
Registrant City: GDPR Masked
Registrant State/Province: Sofia
Registrant Postal Code: GDPR Masked
Registrant Country: BG
Registrant Phone: GDPR Masked
Registrant Phone Ext: 
Registrant Fax: GDPR Masked
Registrant Fax Ext: 
Registrant Email: [email protected]
Registry Admin ID: GDPR Masked
Admin Name: GDPR Masked
Admin Organization: GDPR Masked
Admin Street: GDPR Masked
Admin City: GDPR Masked
Admin State/Province: GDPR Masked
Admin Postal Code: GDPR Masked
Admin Country: GDPR Masked
Admin Phone: GDPR Masked
Admin Phone Ext: 
Admin Fax: GDPR Masked
Admin Fax Ext: 
Admin Email: [email protected]
Registry Tech ID: GDPR Masked
Tech Name: GDPR Masked
Tech Organization: GDPR Masked
Tech Street: GDPR Masked
Tech City: GDPR Masked
Tech State/Province: GDPR Masked
Tech Postal Code: GDPR Masked
Tech Country: GDPR Masked
Tech Phone: GDPR Masked
Tech Phone Ext: 
Tech Fax: GDPR Masked
Tech Fax Ext: 
Tech Email: [email protected]
Name Server: ns1.headfirst.cloud
Name Server: ns2.headfirst.cloud
Name Server: ns3.headfirst.cloud
Name Server: ns4.headfirst.cloud
DNSSEC: signedDelegation
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.2013775952
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T10:46:59Z <<<

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

Registration Service Provided By: CLOUDNS

The data in this whois database is provided to you for information purposes 
only, that is, to assist you in obtaining information about or related to a 
domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree 
that you will use this data only for lawful purposes and that, under no 
circumstances will you use this data to: 
(1) enable high volume, automated, electronic processes that stress or load 
this whois database system providing you this information; or 
(2) allow, enable, or otherwise support the transmission of mass unsolicited, 
commercial advertising or solicitations via direct mail, electronic mail, or 
by telephone. 
The compilation, repackaging, dissemination or other use of this data is 
expressly prohibited without prior written consent from us. The Registrar of 
record is PDR Ltd. d/b/a PublicDomainRegistry.com. 
We reserve the right to modify these terms at any time. 
By submitting this query, you agree to abide by these terms.

% Query time: 998 msec
% WHEN: Thu Oct 01 10:46:58 UTC 2026