Summary
- Registrar
- NETIM
- Status
- clientTransferProhibited
- Created on
- July 8, 2025
- Expires on
- July 8, 2027
- Name servers
- ns1.netim.net, ns2.netim.net, ns3.netim.net
- Mail servers
- mx.zoho.in, mx2.zoho.in, mx3.zoho.in
- 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 makeitla.st but fails SPF and DKIM checks.
- Policy
- Monitoring
- Subdomain policy
- Monitoring
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- —
- Failure reports
- —
Record
v=DMARC1; p=none;
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 makeitla.st.
| Rule | Value | Result |
|---|---|---|
| include | zoho.in | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 include:zoho.in ~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 makeitla.st arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from makeitla.st 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 @makeitla.st 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
makeitla.st MX 10 mx1.makeitla.st. makeitla.st MX 20 mx2.makeitla.st.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.makeitla.st.
- 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
makeitla.st 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.makeitla.st, 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.makeitla.st 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.makeitla.st, 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.makeitla.st 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 makeitla.st
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 |
|---|---|
| ns1.netim.net | 198.50.216.33 |
| ns2.netim.net | 192.174.68.97 |
| ns3.netim.net | 176.97.158.97 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @makeitla.st 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 | mx.zoho.in | 169.148.149.118 |
| 20 | mx2.zoho.in | 169.148.149.118 |
| 50 | mx3.zoho.in | 169.148.146.168 |
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.makeitla.st.
| Name | Content |
|---|---|
| makeitla.st | v=spf1 include:zoho.in ~all |
| makeitla.st | google-site-verification=6XEZIiJSCfB5WuTfTqbAPdfrabgRIdd8JxP7mSd5QHE |
| _dmarc.makeitla.st | v=DMARC1; p=none; |
Related IP addresses
IPv4 addresses used by makeitla.st: 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 |
| 198.50.216.33 | Name server ns1.netim.net | 198.50.216.0/24 |
| 192.174.68.97 | Name server ns2.netim.net | 192.174.68.0/24 |
| 176.97.158.97 | Name server ns3.netim.net | 176.97.158.0/24 |
| 169.148.149.118 | Mail server mx.zoho.in, Mail server mx2.zoho.in | 169.148.149.0/24 |
| 169.148.146.168 | Mail server mx3.zoho.in | 169.148.146.0/24 |
WHOIS of the domain makeitla.st
Whois Server Version 3.3.2 Domain Name: makeitla.st Registrar: NETIM Name Server: ns1.netim.net Name Server: ns2.netim.net Name Server: ns3.netim.net Status: clientTransferProhibited Updated Date: 2026-07-03 Creation Date: 2025-07-08 Expiration Date: 2027-07-08 >>> Last update of whois database: 2026-10-02T22:30:36Z <<< The data in the WHOIS database is protected by copyright. By submitting a WHOIS query, you agree that you will use this data only for lawful purposes according with the terms and policy that is publicly available on https://www.nic.st/terms-of-service and that, under no circumstances will you use this data to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; in contravention of any applicable data and privacy protection laws; or to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without ST Registry prior written permission. By executing this query, in any manner whatsoever, you agree to abide by these terms. In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. ST Registry reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. DOMAIN: makeitla.st REGISTRATION-SERVICE-PROVIDER: NETIM URL: www.netim.com created-date: 2025-07-08 20:32:17 updated-date: 2026-07-03 11:32:57 expiration-date: 2027-07-08 20:32:17 registrant-organization: GDPR protected registrant-name: GDPR protected (GDPR protected) registrant-street: GDPR protected registrant-city: GDPR protected registrant-state: GDPR protected registrant-zip: GDPR protected registrant-country: FR registrant-phone: GDPR protected registrant-fax: GDPR protected registrant-email: GDPR protected admin-organization: GDPR protected admin-name: GDPR protected (GDPR protected) admin-street: GDPR protected admin-city: GDPR protected admin-state: GDPR protected admin-zip: GDPR protected admin-country: FR admin-phone: GDPR protected admin-fax: GDPR protected admin-email: GDPR protected tech-organization: GDPR protected tech-name: GDPR protected (GDPR protected) tech-street: GDPR protected tech-city: GDPR protected tech-state: GDPR protected tech-zip: GDPR protected tech-country: FR tech-phone: GDPR protected tech-fax: GDPR protected tech-email: GDPR protected billing-organization: GDPR protected billing-name: GDPR protected (GDPR protected) billing-street: GDPR protected billing-city: GDPR protected billing-state: GDPR protected billing-zip: GDPR protected billing-country: FR billing-phone: GDPR protected billing-fax: GDPR protected billing-email: GDPR protected nameserver: ns1.netim.net nameserver: ns2.netim.net nameserver: ns3.netim.net % Query time: 865 msec % WHEN: Fri Oct 02 22:30:36 UTC 2026