Summary
- Registrar
- Ascio Technologies, Inc. - Denmark
- Status
- ok
- Created on
- February 17, 2016
- Expires on
- February 17, 2027
- Name servers
- ns-auth-02.bahnhof.net, ns-auth-01.bahnhof.net
- Mail servers
- mail.bahnhof.se
- SPF
- Strict
- DKIM
- No key found among the common selectors
- Website
- See the website
Authorized senders (SPF)
E-mails sent by any other server are rejected.
SPF lists the servers allowed to send e-mails for bahnhof.cloud.
| Rule | Value | Result |
|---|---|---|
| a | — | Allowed |
| mx | — | Allowed |
| a | mx.bahnhof.net | Allowed |
| ip4 | 94.254.0.162 | Allowed |
| include | _msspf.bahnhof.net | Allowed |
| include | _spf.bahnhof.net | Allowed |
| all | — | Rejected |
Top-level DNS lookups: 5 of 10 allowed
Record
v=spf1 a mx a:mx.bahnhof.net ip4:94.254.0.162 include:_msspf.bahnhof.net include:_spf.bahnhof.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 bahnhof.cloud arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from bahnhof.cloud 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 @bahnhof.cloud 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
bahnhof.cloud MX 10 mx1.bahnhof.cloud. bahnhof.cloud MX 20 mx2.bahnhof.cloud.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.bahnhof.cloud.
- 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
bahnhof.cloud 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.bahnhof.cloud, 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.bahnhof.cloud 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.bahnhof.cloud, 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.bahnhof.cloud 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 bahnhof.cloud
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 | 155.4.244.88 |
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 |
|---|---|
| ns-auth-02.bahnhof.net | 158.174.209.18 |
| ns-auth-01.bahnhof.net | 158.174.209.10 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @bahnhof.cloud 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 |
|---|---|---|
| 1 | mail.bahnhof.se | 213.136.33.1 |
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.bahnhof.cloud.
| Name | Content |
|---|---|
| bahnhof.cloud | google-site-verification=SSDDafo4d-KI9MaKbptny_6DNuZmhq9Potq7VcsS30E |
| bahnhof.cloud | v=spf1 a mx a:mx.bahnhof.net ip4:94.254.0.162 include:_msspf.bahnhof.net include:_spf.bahnhof.net -all |
Related IP addresses
IPv4 addresses used by bahnhof.cloud: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 155.4.244.88 | Website | 155.4.244.0/24 |
| 158.174.209.18 | Name server ns-auth-02.bahnhof.net | 158.174.209.0/24 |
| 158.174.209.10 | Name server ns-auth-01.bahnhof.net | 158.174.209.0/24 |
| 213.136.33.1 | Mail server mail.bahnhof.se | 213.136.33.0/24 |
| 94.254.0.162 | Authorized by SPF | 94.254.0.0/24 |
WHOIS of the domain bahnhof.cloud
Domain Name: bahnhof.cloud Registry Domain ID: DD64EDEBD4A644A7C970194D677934EC8-ARI Registrar WHOIS Server: whois.ascio.com Registrar URL: http://www.ascio.com/ Updated Date: 2026-04-03T06:28:18.116Z Creation Date: 2016-02-17T06:27:28.764Z Registry Expiry Date: 2027-02-17T06:27:28.764Z Registrar: Ascio Technologies, Inc. - Denmark Registrar IANA ID: 106 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +45.33886100 Domain Status: ok https://icann.org/epp#ok Name Server: ns-auth-01.bahnhof.net Name Server: ns-auth-02.bahnhof.net DNSSEC: unsigned URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf >>> Last update of WHOIS database: 2026-10-01T15:51:43.847Z <<< For more information on domain status codes, please visit https://icann.org/epp The WHOIS information provided in this page has been redacted in compliance with ICANN's Temporary Specification for gTLD Registration Data. The data in this record is provided by Tucows Registry for informational purposes only, and it does not guarantee its accuracy. Tucows Registry is authoritative for whois information in top-level domains it operates under contract with the Internet Corporation for Assigned Names and Numbers. Whois information from other top-level domains is provided by a third-party under license to Tucows Registry. This service is intended only for query-based access. By using this service, you agree that you will use any data presented only for lawful purposes and that, under no circumstances will you use (a) data acquired for the purpose of allowing, enabling, or otherwise supporting the transmission by e-mail, telephone, facsimile or other communications mechanism of mass unsolicited, commercial advertising or solicitations to entities other than your existing customers; or (b) this service to enable high volume, automated, electronic processes that send queries or data to the systems of any Registrar or any Registry except as reasonably necessary to register domain names or modify existing domain name registrations. Tucows Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. All rights reserved. Domain Name: bahnhof.cloud Registrar WHOIS Server: whois.ascio.com Registrar URL: http://www.ascio.com Updated Date: 2026-02-18T00:33:40Z Creation Date: 2021-02-03T10:21:14Z Registrar Registration Expiration Date: 2027-02-17T00:00:00Z Registrar: Ascio Technologies, Inc Registrar IANA ID: 106 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +44 (20) 81583881 Domain Status: OK https://icann.org/epp#ok Registry Registrant ID: Not Disclosed Registrant Name: Not Disclosed Registrant Organization: Not Disclosed Registrant Street: Not Disclosed Registrant City: Not Disclosed Registrant State/Province: Registrant Postal Code: Not Disclosed Registrant Country: SE Registrant Phone: Not Disclosed Registrant Phone Ext: Not Disclosed Registrant Fax: Not Disclosed Registrant Fax Ext: Not Disclosed Registrant Email: https://whoiscontact.ascio.com?domainname=bahnhof.cloud Registry Admin ID: Not Disclosed Admin Name: Not Disclosed Admin Organization: Not Disclosed Admin Street: Not Disclosed Admin City: Not Disclosed Admin State/Province: Not Disclosed Admin Postal Code: Not Disclosed Admin Country: Not Disclosed Admin Phone: Not Disclosed Admin Phone Ext: Not Disclosed Admin Fax: Not Disclosed Admin Fax Ext: Not Disclosed Admin Email: Not Disclosed Registry Tech ID: Not Disclosed Tech Name: Not Disclosed Tech Organization: Not Disclosed Tech Street: Not Disclosed Tech City: Not Disclosed Tech State/Province: Not Disclosed Tech Postal Code: Not Disclosed Tech Country: Not Disclosed Tech Phone: Not Disclosed Tech Phone Ext: Not Disclosed Tech Fax: Not Disclosed Tech Fax Ext: Not Disclosed Tech Email: Not Disclosed Name Server: ns-auth-01.bahnhof.net Name Server: ns-auth-02.bahnhof.net DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: https://icann.org/wicf >>> Last update of WHOIS database: 2026-10-01T15:51:44Z <<< For more information on Whois status codes, please visit https://icann.org/epp The data in Ascio Technologies' WHOIS database is provided by Ascio Technologies for information purposes only. By submitting a WHOIS query, you agree that you will use this data only for lawful purpose. In addition, you agree not to: (a) use the data to allow, enable, or otherwise support any marketing activities, regardless of the medium used. Such media include but are not limited to e-mail, telephone, facsimile, postal mail, SMS, and wireless alerts; or (b) use the data to enable high volume, automated, electronic processes that send queries or data to the systems of any Registry Operator or ICANN-Accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. (c) sell or redistribute the data except insofar as it has been incorporated into a value-added product or service that does not permit the extraction of a substantial portion of the bulk data from the value-added product or service for use by other parties. Ascio Technologies reserves the right to modify these terms at any time. Ascio Technologies cannot guarantee the accuracy of the data provided. By accessing and using Ascio Technologies WHOIS service, you agree to these terms. % Query time: 889 msec % WHEN: Thu Oct 01 15:51:43 UTC 2026