Dataweaz

karisma.org.co

Summary

Registrar
www.registrocolombia.co
Status
clientTransferProhibited
Created on
August 4, 2004
Expires on
August 9, 2028
Name servers
singapore1.muutta.org
Mail servers
mail.protonmail.ch, mailsec.protonmail.ch

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 karisma.org.co but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=none; pct=5; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=reject

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for karisma.org.co.

RuleValueResult
include_spf.google.comAllowed
include_spf.protonmail.chAllowed
all—Rejected

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:_spf.google.com include:_spf.protonmail.ch -all

E-mail signing (DKIM)

DKIM keys published by karisma.org.co under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
protonmail2Proton MailRSA 2048 bitsActive
protonmail3Proton MailRSA 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 karisma.org.co arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from karisma.org.co 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 @karisma.org.co 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

karisma.org.co  MX  10 mx1.karisma.org.co.
karisma.org.co  MX  20 mx2.karisma.org.co.

What the record contains

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

karisma.org.co  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.karisma.org.co, 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.karisma.org.co  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.karisma.org.co, 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.karisma.org.co  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 karisma.org.co

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.

TypeIP address
A5.9.111.213

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
singapore1.muutta.org188.166.235.83

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @karisma.org.co 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.protonmail.ch176.119.200.128
20mailsec.protonmail.ch185.70.42.129

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.karisma.org.co.

NameContent
karisma.org.coprotonmail-verification=a7fd85390e92df0cb1df81fa3211e9af7370b976
karisma.org.cov=spf1 include:_spf.google.com include:_spf.protonmail.ch -all
_dmarc.karisma.org.cov=DMARC1; p=none; pct=5; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=reject
google._domainkey.karisma.org.cov=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAq4bWONKoyRpXNY5sVAzaPHxb88SVYVL+sRsEA3l9zmtnpLot5Rscb09W1f4UxZiE+W+jbFqP+X+KN1sf4OqRYFE029hllFaASpaIkyQkLxoYRFkOJVqXU32IJISCuCq7NEe5DxCqx/fgozy/XrXAfwMPJAmxsGchB7/5/Mm5oDTGODDS0DcIRYP/jRKxYkVykVnS8tT+2AT9566BkWkahSqGmbmFfQndklK4nZUGZVXZANE11LPT2diUEZpdlz3figYWiwcdwVs2B8s5qR5f2hhNXEHAwKdWcPkrGF1e90K0pEKv8XiVe9SYsmLcWMX5NbRDWPF6muIwtpXkFwRHgwIDAQAB
protonmail2._domainkey.karisma.org.cov=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtrQ85NHrfjRYb8m1GHn/q5DDdEESp0a7Ker2xqoPH7hk6ETQrXRy2bRUl1WSw8EDOmLZJWMW4670WZnrVqgKwWGoZD70evpTCIOIQnYAIxQMMZemVJn8sSfhFw1C4y+G/bGDhDsLcRMPKQBhJAuZ9PmFcz3Y3TxLnyB0zvFCZWEzh89BhxVIGlkBtGCyPVvnfhBSN2hm+h5ZugZP03juqftzOdy0nNSMNR73SqLQvdqpe5Wn2keGWCma6NfezITOw+HFJkIMgRpwobjW1H51+hGnvC3SGxCo9tLMxHW6RfU1dzZcrHJIoKzp7OO5iJz9+40epKDrcrWuKeGKrqvj5wIDAQAB;
protonmail3._domainkey.karisma.org.cov=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtYheBy5WaXovtj53tF47zVSNVQ9RW0GbQ3gMOldgfpjfXzQkULXeR1/u0+iuXAML9PjGnDB0Fo7xzS77FSvYe4iK7JTlXA8c5peqYFtcOzU8EmyhFae8QWUfzns0EBPFcF2sWb7ieyyK3j9Iam1ZTce7OcMA64XZd2Ca+eSAcHWiGyUQBflkWAkKs0Ts1caJX1e+zzQChkwa/VpV0lbA+UQ/5IQMRdCuapvw61n12FTJCjjqJ8KUU55pPSQTWynfibakUipaFCcAAetV8yQw3qXrDxFRETMV7AN3iVR4Qcof+PyBJn+4fj+nLU0HKbNEgZ1hjuWXq7CeQOX90U//hQIDAQAB;

Related IP addresses

IPv4 addresses used by karisma.org.co: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
5.9.111.213Website5.9.111.0/24
188.166.235.83Name server singapore1.muutta.org188.166.235.0/24
176.119.200.128Mail server mail.protonmail.ch176.119.200.0/24
185.70.42.129Mail server mailsec.protonmail.ch185.70.42.0/24

WHOIS of the domain karisma.org.co

Domain Name: KARISMA.ORG.CO
Registry Domain ID: D58754-CNIC
Registrar WHOIS Server: whois.registry.co
Registrar URL: http://www.registrocolombia.co
Updated Date: 2024-07-28T22:24:03.0Z
Creation Date: 2004-08-04T00:00:00.0Z
Registry Expiry Date: 2028-08-08T23:59:59.0Z
Registrar: www.registrocolombia.co
Registrar IANA ID: 111111
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ASIA1.MUUTTA.ORG
Name Server: SINGAPORE1.MUUTTA.ORG
DNSSEC: unsigned
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +57.3127823611
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-02T15:06:17.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.

% Query time: 557 msec
% WHEN: Fri Oct 02 15:06:17 UTC 2026