Summary
- Registrar
- Amazon Registrar, Inc.
- Status
- ok
- Created on
- December 31, 2022
- Expires on
- December 31, 2026
- Name servers
- ns4.indiecomp.com, ns3.indiecomp.com, ns1.indiecomp.com, ns2.indiecomp.com
- Mail servers
- mail.protonmail.ch, mailsec.protonmail.ch
- DMARC
- Quarantine
- SPF
- Soft
- DKIM
- 4 keys found
- Website
- See the website
Spoofing protection (DMARC)
E-mails spoofing this domain are sent to spam.
DMARC tells mail servers what to do with an e-mail that claims to come from fediforum.org but fails SPF and DKIM checks.
- Policy
- Quarantine
- Subdomain policy
- Quarantine
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- [email protected]
- Failure reports
- [email protected]
Record
v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
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 fediforum.org.
| Rule | Value | Result |
|---|---|---|
| include | _spf.mlsend.com | Allowed |
| include | _spf.protonmail.ch | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 2 of 10 allowed
Record
v=spf1 include:_spf.mlsend.com include:_spf.protonmail.ch ~all
E-mail signing (DKIM)
DKIM keys published by fediforum.org under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| k2 | Mailchimp | RSA 2048 bits | Active |
| k3 | Mailchimp | RSA 2048 bits | Active |
| protonmail | Proton Mail | RSA 2048 bits | Active |
| protonmail3 | Proton Mail | RSA 2048 bits | Active |
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 fediforum.org arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from fediforum.org 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 @fediforum.org 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
fediforum.org MX 10 mx1.fediforum.org. fediforum.org MX 20 mx2.fediforum.org.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.fediforum.org.
- 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
fediforum.org 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.fediforum.org, 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.fediforum.org 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.fediforum.org, 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.fediforum.org 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 fediforum.org
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 | 54.198.255.93 |
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.indiecomp.com | 205.251.192.44 |
| ns3.indiecomp.com | 205.251.198.113 |
| ns1.indiecomp.com | 205.251.197.241 |
| ns2.indiecomp.com | 205.251.194.127 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @fediforum.org 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 | mail.protonmail.ch | 185.70.42.128 |
| 20 | mailsec.protonmail.ch | 185.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.fediforum.org.
| Name | Content |
|---|---|
| fediforum.org | protonmail-verification=0c8ba0e627dca6b21e312e4f50c36656805fcf89 |
| fediforum.org | v=spf1 include:_spf.mlsend.com include:_spf.protonmail.ch ~all |
| fediforum.org | google-site-verification=j3TPuWPo7JSqo7kiaGtNV8_sPVrd6P2bPBLkHVWlsvk |
| fediforum.org | mailerlite-domain-verification=c9aeaa8857f30420356dae9cc7c75644f2e7911a |
| _dmarc.fediforum.org | v=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1 |
| k2._domainkey.fediforum.org | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB; |
| k3._domainkey.fediforum.org | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB; |
| protonmail._domainkey.fediforum.org | v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArki9boCvhRYSGLEX8BG1MifcyT55m8cd5VAI6cGSyF+ez/FsF6I/+urNv3cvC+V2zANKIpRT/98hOvuHC2rS67EIiklL09mRpPUfZ7vY4gV9jV24qrD/EsK/LlRLkqU28TkBZNwIbksZAh8mjmOZ/7gumdfOb118+JY9Xm7lnVGS1McSwts7ot3d4gBzD+YvR+CI3murGh1cQyFmd2ECxHgPnYBzMN9vIZ2zlWbg8p3oEdaOkmCfOMxE5hj14t43zv5lKwaL4Re3lrNXOk5STfWkMKVlOZ8xKw6zLp21CCsTTnmuVOZXyCbn58KvDNa3NUMvapDrB+GntdL3jHpxOwIDAQAB; |
| protonmail3._domainkey.fediforum.org | v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3fO2u1LdwXR4uAxVtxn/adGP5RrEa7gXorPpaDw5yUPFy+tyQgKn8X5yviAguMRJ1zbh0cInlD8Ke0dESWfS8d1CXG22dZcNT+n/2opqXB8xWA+H0vShfDDK4xwFeZL6tfgTkYcL9y3mcP2jVpaULBhSqZTGk5D+iPG8sQJZbLmR3AflNx9uFltLE5b9vJbt4U7YnIXUEfSWAsZFLyWuJEQgbGFzK5CKRst6Lc+igLK8aaKq90ycN2vlmhfHRAFaGZ+AK/bV5rtDhzOSlf2PnVSazRd//QUFbj/I4Yyr7FKPw0Dkw8KYwWbFkU0ysWmsjx77ggrhYWdCvDD21PHVeQIDAQAB; |
Related IP addresses
IPv4 addresses used by fediforum.org: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 54.198.255.93 | Website | 54.198.255.0/24 |
| 205.251.192.44 | Name server ns4.indiecomp.com | 205.251.192.0/24 |
| 205.251.198.113 | Name server ns3.indiecomp.com | 205.251.198.0/24 |
| 205.251.197.241 | Name server ns1.indiecomp.com | 205.251.197.0/24 |
| 205.251.194.127 | Name server ns2.indiecomp.com | 205.251.194.0/24 |
| 185.70.42.128 | Mail server mail.protonmail.ch | 185.70.42.0/24 |
| 185.70.42.129 | Mail server mailsec.protonmail.ch | 185.70.42.0/24 |
WHOIS of the domain fediforum.org
Domain Name: fediforum.org Registry Domain ID: REDACTED Registrar WHOIS Server: whois.registrar.amazon Registrar URL: http://registrar.amazon.com Updated Date: 2026-08-12T03:48:18Z Creation Date: 2022-12-31T21:27:09Z Registry Expiry Date: 2026-12-31T21:27:09Z Registrar: Amazon Registrar, Inc. Registrar IANA ID: 468 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.2024422253 Domain Status: ok https://icann.org/epp#ok Name Server: ns1.indiecomp.com Name Server: ns2.indiecomp.com Name Server: ns3.indiecomp.com Name Server: ns4.indiecomp.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-01T21:37:52Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Domain Name: fediforum.org Registry Domain ID: 24100253412019_DOMAIN-KEYSYS Registrar WHOIS Server: whois.registrar.amazon Registrar URL: Updated Date: 2025-12-01T21:31:49Z Creation Date: 2022-12-31T21:27:09Z Registrar Registration Expiration Date: 2026-12-31T21:27:09Z Registrar: Amazon Registrar, Inc. Registrar IANA ID: 468 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact URL: Registrar Abuse Contact Phone: +1.2024422253 Domain Status: ok https://icann.org/epp#ok Registry Registrant ID: Not Available From Registry Registrant Name: On behalf of fediforum.org OWNER Registrant Organization: c/o whoisproxy.com Registrant Street: 604 Cameron Street Registrant City: Alexandria Registrant State/Province: VA Registrant Postal Code: 22314 Registrant Country: US Registrant Phone: +64.48319528 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: d0b1896c5fc9f198e7ff1ab7f7b20caf99a261c486908276a0245a2cd44df960@fediforum.org.whoisproxy.org Registry Admin ID: Not Available From Registry Admin Name: On behalf of fediforum.org ADMIN Admin Organization: c/o whoisproxy.com Admin Street: 604 Cameron Street Admin City: Alexandria Admin State/Province: VA Admin Postal Code: 22314 Admin Country: US Admin Phone: +64.48319528 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: d0b1896c5fc9f198e7ff1ab7f7b20caff51876bb1886bf9baa7aaa07b5177c5e@fediforum.org.whoisproxy.org Registry Tech ID: Not Available From Registry Tech Name: On behalf of fediforum.org TECH Tech Organization: c/o whoisproxy.com Tech Street: 604 Cameron Street Tech City: Alexandria Tech State/Province: VA Tech Postal Code: 22314 Tech Country: US Tech Phone: +64.48319528 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: d0b1896c5fc9f198e7ff1ab7f7b20caffd2479cd402a12bc3b06afae2b5295a0@fediforum.org.whoisproxy.org Registry Billing ID: Not Available From Registry Billing Name: On behalf of fediforum.org BILLING Billing Organization: c/o whoisproxy.com Billing Street: 604 Cameron Street Billing City: Alexandria Billing State/Province: VA Billing Postal Code: 22314 Billing Country: US Billing Phone: +64.48319528 Billing Phone Ext: Billing Fax: Billing Fax Ext: Billing Email: d0b1896c5fc9f198e7ff1ab7f7b20cafe055eeba15428491243d0be0b4d767ce@fediforum.org.whoisproxy.org Name Server: ns1.indiecomp.com Name Server: ns2.indiecomp.com Name Server: ns3.indiecomp.com Name Server: ns4.indiecomp.com DNSSEC: unsigned Whoisprivacy: 1 URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-10-01T21:37:53Z <<< For more information on Whois status codes, please visit https://www.icann.org/epp To contact the registered registrant please proceed to: https://www.domain-contact.org This data is provided by for information purposes, and to assist persons obtaining information about or related to domain name registration records. does 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, you will use this data to 1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via E-mail (spam) or 2) enable high volume, automated, electronic processes that apply to this WHOIS server. These terms may be changed without prior notice. By submitting this query, you agree to abide by this policy. % Query time: 1244 msec % WHEN: Thu Oct 01 21:37:52 UTC 2026