Summary
- Registrar
- NameCheap, Inc.
- Status
- clientTransferProhibited
- Created on
- October 6, 2024
- Expires on
- October 7, 2027
- Name servers
- jacqueline.ns.cloudflare.com, terry.ns.cloudflare.com
- Mail servers
- route1.mx.cloudflare.net, route2.mx.cloudflare.net, route3.mx.cloudflare.net
- DMARC
- Monitoring
- SPF
- Soft
- DKIM
- No key found among the common selectors
- Website
- See the website
Spoofing protection (DMARC)
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 nitro.build 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
- —
Record
v=DMARC1; p=none; rua=mailto:[email protected]
Authorized senders (SPF)
E-mails sent by any other server are accepted but flagged as suspicious.
SPF lists the servers allowed to send e-mails for nitro.build.
| Rule | Value | Result |
|---|---|---|
| include | _spf.mx.cloudflare.net | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 include:_spf.mx.cloudflare.net ~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 nitro.build arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from nitro.build 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 @nitro.build 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
nitro.build MX 10 mx1.nitro.build. nitro.build MX 20 mx2.nitro.build.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.nitro.build.
- 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
nitro.build 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.nitro.build, 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.nitro.build 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.nitro.build, 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.nitro.build 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 nitro.build
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 | 216.150.1.1 |
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 |
|---|---|
| jacqueline.ns.cloudflare.com | 108.162.194.132 |
| terry.ns.cloudflare.com | 173.245.59.237 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @nitro.build 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 |
|---|---|---|
| 14 | route1.mx.cloudflare.net | 162.159.205.12 |
| 19 | route2.mx.cloudflare.net | 162.159.205.17 |
| 86 | route3.mx.cloudflare.net | 162.159.205.24 |
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.nitro.build.
| Name | Content |
|---|---|
| nitro.build | v=spf1 include:_spf.mx.cloudflare.net ~all |
| nitro.build | google-site-verification=ENffPtQDsELZULy8qS8Fp2Z6O7ZiBC2m2AZ-oc2-g7Q |
| _dmarc.nitro.build | v=DMARC1; p=none; rua=mailto:[email protected] |
Related IP addresses
IPv4 addresses used by nitro.build: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 216.150.1.1 | Website | 216.150.1.0/24 |
| 108.162.194.132 | Name server jacqueline.ns.cloudflare.com | 108.162.194.0/24 |
| 173.245.59.237 | Name server terry.ns.cloudflare.com | 173.245.59.0/24 |
| 162.159.205.12 | Mail server route1.mx.cloudflare.net | 162.159.205.0/24 |
| 162.159.205.17 | Mail server route2.mx.cloudflare.net | 162.159.205.0/24 |
| 162.159.205.24 | Mail server route3.mx.cloudflare.net | 162.159.205.0/24 |
WHOIS of the domain nitro.build
Domain Name: NITRO.BUILD Registry Domain ID: D491333166-CNIC Registrar WHOIS Server: whois.namecheap.com Registrar URL: https://namecheap.com Updated Date: 2026-08-31T09:00:11.0Z Creation Date: 2024-10-06T08:31:13.0Z Registry Expiry Date: 2027-10-06T23:59:59.0Z Registrar: NameCheap, Inc. Registrar IANA ID: 1068 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: JACQUELINE.NS.CLOUDFLARE.COM Name Server: TERRY.NS.CLOUDFLARE.COM DNSSEC: unsigned Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.9854014545 URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T15:49:38.0Z <<< For more information on Whois status codes, please visit https://icann.org/epp The registration data available in this service is limited. Additional data may be available at https://lookup.icann.org The Whois and RDAP services are provided by CentralNic, and contain information pertaining to Internet domain names registered by our our customers. By using this service you are agreeing (1) not to use any information presented here for any purpose other than determining ownership of domain names, (2) not to store or reproduce this data in any way, (3) not to use any high-volume, automated, electronic processes to obtain data from this service. Abuse of this service is monitored and actions in contravention of these terms will result in being permanently blacklisted. All data is (c) CentralNic Ltd (https://www.centralnicregistry.com) Access to the Whois and RDAP services is rate limited. For more information, visit https://centralnicregistry.com/policies/whois-guidance. Domain name: nitro.build Registry Domain ID: D491333166-CNIC Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2026-08-31T09:00:11.58Z Creation Date: 2024-10-06T08:31:13.00Z Registrar Registration Expiration Date: 2027-10-06T23:59:59.00Z Registrar: NAMECHEAP INC Registrar IANA ID: 1068 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.9854014545 Reseller: NAMECHEAP INC Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: Registrant Name: Redacted for Privacy Purposes Registrant Organization: Privacy service provided by WITHHELD FOR PRIVACY LLC Registrant Street: 16192 Coastal Highway Registrant City: Lewes Registrant State/Province: Delaware Registrant Postal Code: 19958 Registrant Country: US Registrant Phone: +1.3022061391 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] Registry Admin ID: Admin Name: Redacted for Privacy Purposes Admin Organization: Privacy service provided by WITHHELD FOR PRIVACY LLC Admin Street: 16192 Coastal Highway Admin City: Lewes Admin State/Province: Delaware Admin Postal Code: 19958 Admin Country: US Admin Phone: +1.3022061391 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: [email protected] Registry Tech ID: Tech Name: Redacted for Privacy Purposes Tech Organization: Privacy service provided by WITHHELD FOR PRIVACY LLC Tech Street: 16192 Coastal Highway Tech City: Lewes Tech State/Province: Delaware Tech Postal Code: 19958 Tech Country: US Tech Phone: +1.3022061391 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: [email protected] Name Server: jacqueline.ns.cloudflare.com Name Server: terry.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-09-30T19:49:38.93Z <<< For more information on Whois status codes, please visit https://icann.org/epp % Query time: 1216 msec % WHEN: Thu Oct 01 15:49:37 UTC 2026