Dataweaz

simmy.org

Summary

Registrar
http.net Internet GmbH
Status
clientTransferProhibited
Created on
November 3, 2023
Expires on
November 3, 2026
Name servers
ns2.hosting.de, ns1.hosting.de, ns3.hosting.de
Mail servers
mail.simmy.org

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 simmy.org 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)

Neutral

The record gives no instruction for other servers.

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

RuleValueResult
includespf.mailjet.comAllowed
includespf.hosting.deAllowed
all—Neutral

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:spf.mailjet.com include:spf.hosting.de ?all

E-mail signing (DKIM)

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

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

simmy.org  MX  10 mx1.simmy.org.
simmy.org  MX  20 mx2.simmy.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.simmy.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

simmy.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.simmy.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.simmy.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.simmy.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.simmy.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 simmy.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.

TypeIP address
A85.195.229.95

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
ns2.hosting.de194.50.113.2
ns1.hosting.de134.0.30.178
ns3.hosting.de194.126.196.2

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @simmy.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.

PriorityServerIP address
16mail.simmy.org85.195.229.95

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.simmy.org.

NameContent
simmy.orggoogle-site-verification=61W4B5ZE5bx0LN68aXDrOCWHfp3tS-Sw1ixGTANibnE
simmy.orgv=spf1 include:spf.mailjet.com include:spf.hosting.de ?all
_dmarc.simmy.orgv=DMARC1; p=none; rua=mailto:[email protected]
mailjet._domainkey.simmy.orgk=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYiZAUFiMMd/agO8c0/coeEpUbgR4mhMDwqmAzPsWvAkXSPsTa4FsxYo/ph5EXcGBb0GEulz5Xq9Kl58wSe3s+FbJ35FOjWbsG5o27AVnmqFsTuWMyB+u4CoRWvQUNefLgtWeoG+hOAeaP5rKogUj4wV16z/CkXTocVs/gLomVjbyDW7u0AP9Njn5roQkFecj8h5VvXqarfXdLyasQ/fA0rzCU4gLFrKzqHcOhjFh2YoEX8Dt7woFz5A6AHOJdhryxNHTYbMdxlc5vXaNxjLoEc2w6onI2TgJru1shRpNCYHQ7f8QMzbiGLSV2l+/dnIOuVH7ritha6bTZfWt2HAJwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
85.195.229.95Website, Mail server mail.simmy.org85.195.229.0/24
194.50.113.2Name server ns2.hosting.de194.50.113.0/24
134.0.30.178Name server ns1.hosting.de134.0.30.0/24
194.126.196.2Name server ns3.hosting.de194.126.196.0/24

WHOIS of the domain simmy.org

Domain Name: simmy.org
Registry Domain ID: REDACTED
Registrar WHOIS Server: http://rdap.routing.net
Registrar URL: http://www.http.net
Updated Date: 2026-08-12T00:44:12Z
Creation Date: 2023-11-03T15:25:41Z
Registry Expiry Date: 2026-11-03T15:25:41Z
Registrar: http.net Internet GmbH
Registrar IANA ID: 976
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +49.24146314115
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns1.hosting.de
Name Server: ns2.hosting.de
Name Server: ns3.hosting.de
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T14:21:18Z <<<

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: simmy.org
Registry Domain ID: 199f1f3281e74716b2d28a55edb42aca-LROR
Registrar WHOIS Server: rdap.routing.net
Registrar URL: https://www.http.net
Updated Date: 2023-11-03T15:25:42Z
Creation Date: 2023-11-03T00:00:00Z
Registrar Registration Expiration Date: 2026-11-03T00:00:00Z
Registrar: http.net Internet GmbH
Registrar IANA ID: 976
Registrar Abuse Contact Email: abuse @ http.net
Registrar Abuse Contact Phone: +49.24146314115
Reseller:
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Registrant State/Province: 
Registrant Country: CH
Registrant Email: [email protected]
Admin Email: [email protected]
Tech Email: [email protected]
Name Server: ns1.hosting.de
Name Server: ns2.hosting.de
Name Server: ns3.hosting.de
DNSSEC: unsigned

URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/

>>> Last update of WHOIS database: 2026-10-01T14:21:19Z <<<

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

RDAP URL: https://rdap.routing.net/domain/simmy.org

The data in the http.net WHOIS database is provided by
http.net Internet GmbH for informational purposes only, to assist you in
obtaining information about or related to a domain name registration
record. http.net provides this information "as is", and
does not guarantee its accuracy. By submitting a WHOIS query, you
agree that you will only use this data for lawful purposes. That,
under no circumstances will you use this data to:
			
1. allow, enable, or otherwise support the transmission of mass or bulk unsolicited,
commercial advertising or solicitations via electronic mail, also known as (SPAM).
2. enable high volume, automated, electronic processes that apply to BulkRegister (or its systems).
				
The compilation, repackaging, dissemination or any other use of this data
is expressly prohibited without the prior written agreement of http.net.
http.net reserves the right to terminate your access to the http.net WHOIS
database in its sole discretion. Including without limitation, for excessive
querying of the WHOIS database or for failure to otherwise abide by this
policy.
				
http.net reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

% Query time: 1252 msec
% WHEN: Thu Oct 01 14:21:17 UTC 2026