Dataweaz

franke.com

Summary

Registrar
Abion AB
Status
clientTransferProhibited
Created on
March 18, 1996
Expires on
March 19, 2027
Name servers
a.portsdns.se, b.portsdns.net
Mail servers
franke-com.t-v1.mx.microsoft
DMARC
Reject
SPF
Soft

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from franke.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Failure reports
—

Record

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected];

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for franke.com.

RuleValueResult
ip4149.72.160.224Allowed
include_spf-dc12.successfactors.comAllowed
include_spf.google.comAllowed
includespf.protection.outlook.comAllowed
include_spf1.franke.comAllowed
include_spf2.franke.comAllowed
includemktomail.comAllowed
all—Suspicious

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 ip4:149.72.160.224 include:_spf-dc12.successfactors.com include:_spf.google.com include:spf.protection.outlook.com include:_spf1.franke.com include:_spf2.franke.com include:mktomail.com ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
selector1Microsoft 365RSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
mailjetMailjetRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

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

franke.com  MX  10 mx1.franke.com.
franke.com  MX  20 mx2.franke.com.

What the record contains

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

franke.com  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.franke.com, 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.franke.com  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.franke.com, 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.franke.com  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 franke.com

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.

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
a.portsdns.se45.54.35.101
b.portsdns.net94.16.23.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @franke.com 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
0franke-com.t-v1.mx.microsoft52.101.91.153

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.franke.com.

NameContent
franke.comgoogle-site-verification=OrdQ_s_Hj3MNs9eoBPsG4-KB_qlORk04HsxbXpXEj0Q
franke.comgoogle-site-verification=GL1Zp14oh0X6h0tWXAc-7cm-rYjqT_ZK6I6TE8hDGK8
franke.comgoogle-site-verification=4486bYXAL2mbULCgUxVOwaxoo5c7H3XGksP_xdSLxR0
franke.comextensis-domain-verification=59354d0f-84e7-48d4-9e02-e4fb4a3f4c8b
franke.comanthropic-domain-verification-xza86r=2q5d04jjr38aysfPe9MNGBRSj
franke.comonetrust-domain-verification=92825acffcf1422d8ad04f16dd2b1d42
franke.comteamviewer-sso-verification=6e0ae5802aad497395d4ab558ffdca86
franke.compinterest-site-verification=d218e4af020db97fd6b46d666de25156
franke.comsmartsheet-site-validation=cuqDm-aEE235A_6Ds3SpV6D6-850nzlO
franke.comfacebook-domain-verification=gfnudrmi5c3lnn0yz9561vvukhek4p
franke.comdocusign=f4403085-0e8a-4030-8c63-9cc2497cd173
franke.comdocusign=27499dd6-dfd5-4dab-9e05-000eb52c3a60
franke.comibmid=e855405d-5d7e-4e04-b7ee-13d54374c86c
franke.comapple-domain-verification=3IP9lo6ejFwS1nVx
franke.comzfhhs0cdz2897c7qdy08kptxk91yph23
franke.comMS=ms25626623
franke.comv=spf1 ip4:149.72.160.224 include:_spf-dc12.successfactors.com include:_spf.google.com include:spf.protection.outlook.com include:_spf1.franke.com include:_spf2.franke.com include:mktomail.com ~all
franke.comfigma-domain-verification=15c550dc95b36d08be7a7f14059c29a3a69dcd729b1363e3e431b9be77ce58bf-1743068579
franke.comatlassian-domain-verification=H6bG21Rhrki0Y7rGOaiC/va5KcZ4ym6uvqDbq4x3aCAatM0InL96U7eZMA6wdLWA
franke.comzapier-domain-verification-challenge=d74e0bd5-e8ff-4d01-9aed-3b2e4a8e4a5f
franke.comtrustpilot-one-time-verification-id=40ac70de-c1d5-4daa-9864-06da00cc5f57
franke.comgoogle-site-verification=RRZTwNl9dLaVQfXujQBHt6vMxlphrzWxXDrgqYQjY50
_dmarc.franke.comv=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected];
google._domainkey.franke.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAjKsAcDGpVtLqYX7ewqkzWkJppWzmdIU8l9YMba23o+Ch/Gps/iQxJr3ob/f07z5I+RUzAzamK8D8GIkRQ+q/lw+SeGFStUML4ZWjEk2t5iN0Qzt9idXIM7c0DtL0uS0R8FVtIsgb6QMlNyPEjHV2GrGMgjUmha5Se8hmZ3cZIFs4WZFxYHvumUMzY17QhRsl8AC3NbutfnQf8zDkp16eNY/5x7LhMQYC2iuAv7921n0OCAnkzVzOvn4nmbl7tBUb+d3A0H60+HrWnV5uRJ/c2DWkoEq0xRbivH9SZ6DKAAbDXUFsYX1+3dEvFLdcfq5ml+R7vp1rfyFVVEuhZCFEqwIDAQAB
selector1._domainkey.franke.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA75wqWBIwRoAmaQMVv2mbr37XzQ5UIy4fPm3tQH7TmQggIrbHFs41KfTxcHhMINMTGM1PeCnZr0xp9dhUCmKK/Xx4pbFShBw2Fg32Gh3tbTsY+C8XNPDJoaVEngu1yaDzfSHr1xxQEiEo/B/cKLyCszWiD6RCBtq+MqhuDIVCEmrzEkshJ3K1JdiCZAQyXgVwX14EnnpmdamS+uDLttkIMC0r0w6+lX+EeXocFhqIJkWaafcR6ztz2NEP2TetiF9Su6g1hNeHmZUN2zcQY19+095HjLzo4WPI0TtgdZ7Fas/EigxoUlyvj5gJcGmgwHHkFthczTRmprMVAadF485ZJQIDAQAB;
s1._domainkey.franke.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3Io3QDm1FsmOSIUe5vyqBEaOQ4Q9PsylNgngkIx4XVrlDpPMRzj9YC1SJQofuGpLFnY2IDdQ+jUuS/eTke5T+2OuSvc5gC05fVrQ5dHSEbKgiJvzE3nNXzeGMq/ffHzD+8M8tL5OhJAxbZdXgnDnh7r0gHwHQZUKWcp/tXG7YG1O0o3oiroJrvUacBxwvMKA0VgsxAfGskLZ89gGZgTsiLxQs1y+rnYOoFMdS113skSxDHuhb0qghbvUm0a22Zd3ViJK5AENq5H2TOMCP3VCANzL47Ds2xl/Eysd7kED7yjeB/CGL0SAWaRBcWPJtV8z0hY2Z2wCrhwNeO7ah92nFQIDAQAB
s2._domainkey.franke.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDdnQk5rnY7/kz7DnCxmydzXVlSDmLccLgiXUcT986s4euWW1pftM1K6l5R5W+7YcIHgvdMZsOlaaiiKUGVGR7hYjMlU56DT/97ttBIUwZxl/crB95tB802T77c6y09Ltq8aI4103LWOUwVP75r1EZk+iTIA6Ncxr+fSIzn5LuCXwIDAQAB
mailjet._domainkey.franke.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCpp5foFbdxMF6YjW7S7bbrw7uF+w6QogdxYIN129ABsj5jNW6kH+P+EojVGJL9OMSobewd7wxHJJ/Iz1kfy5+IpIfGYSszt8WJw3vXNZywPRp1MnqjvpsWE/+njOCBekaoWZ9pb8QuvvlkHCEmuMl39Z2KHjTp2nr60vYyjPzjFwIDAQAB

Related IP addresses

IPv4 addresses used by franke.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
151.101.67.42Website151.101.67.0/24
151.101.131.42Website151.101.131.0/24
151.101.195.42Website151.101.195.0/24
151.101.3.42Website151.101.3.0/24
45.54.35.101Name server a.portsdns.se45.54.35.0/24
94.16.23.1Name server b.portsdns.net94.16.23.0/24
52.101.91.153Mail server franke-com.t-v1.mx.microsoft52.101.91.0/24
149.72.160.224Authorized by SPF149.72.160.0/24

WHOIS of the domain franke.com

Domain Name: FRANKE.COM
   Registry Domain ID: 4274807_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.abion.com
   Registrar URL: http://www.abion.com
   Updated Date: 2026-04-20T12:15:15Z
   Creation Date: 1996-03-18T05:00:00Z
   Registry Expiry Date: 2027-03-19T04:00:00Z
   Registrar: Abion AB
   Registrar IANA ID: 73
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +46.707260015
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: A.PORTSDNS.SE
   Name Server: B.PORTSDNS.NET
   DNSSEC: signedDelegation
   DNSSEC DS Data: 38920 13 2 B48AEEC3E4A248ED4C32E24C9EE04B87D9FB7B57A81E1A407EE9A28A74598D00
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T11:03:43Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.