SPF Check:
spf.dmgmori.com

1. Specify domain name

Enter a domain to be checked for the SPF record
2. Specify IP address (optional)
Enter any IP address to check if it is authorized to send e-mails by the SPF record

What is the SPF lookup for?

With the SPF lookup you analyze the SPF record of a domain for errors, security risks and authorized IP addresses. Optionally, you can specify an IP address to check if it is authorized to send e-mail on behalf of the domain. The SPF lookup analyzes registered TXT records in real time. If you want to specify an SPF record manually, use the SPF Analyzer.

Loading...

SPF check passed

Your SPF record check result
  •   SPF record found
  •   Syntax check: 0 errors
  •   Email Anti-Spoofing: Good
Warning: Compliance breach for email deliverability & security

The domain spf.dmgmori.com does not fulfil the requirements for optimal deliverability to Google, Yahoo and other email service providers.

Mandatory IT baseline protection measures for email security are not fulfilled. There are risks of email misuse.

Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain spf.dmgmori.com.
The SPF record for spf.dmgmori.com is valid.
The syntax check of the SPF record shows no obvious errors.

Which IP-s are legitimate to send emails?
The SPF record contains a reference to external rules, which means that the validity of the SPF record depends on at least one other domain. A detailed list of the rules used externally can be found in the analysis result. In total, 59 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 23.12.2024 at 16:05:07 clock.

Lookup for the domain:
spf.dmgmori.com
IP address to be checked:
no IP address specified
Solve your problems in no time
Guaranteed measurable improvement for email deliverability and domain security
Solve your problems in no time

Evaluation for the domain spf.dmgmori.com 

Nameserverset:
ns2.xc-ns.de
ns5.xc-ns.de
ns6.xc-ns.de
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
193.158.58.192/26
Deutsche Telekom AG blacklist 
62.153.207.0/27
Deutsche Telekom AG blacklist 
162.144.64.224 UNIFIEDLAYER-AS-1 blacklist 
202.248.122.50 FUJITSU LIMITED blacklist 
60.43.159.108 NTT Communications Corporation blacklist 
20.113.182.182 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.218.254.235 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.218.254.237 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.113.150.73 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
35.80.141.6 AMAZON-02 blacklist 
44.229.121.55 AMAZON-02 blacklist 
74.217.54.250/31
INTERNAP-BLK3 blacklist 
49.255.152.93/31
Vocus Connect International Backbone blacklist 
74.121.167.29 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
74.121.167.30 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
88.205.100.160/27
HKN GmbH blacklist 
213.9.75.59 HKN GmbH blacklist 
213.9.75.60 HKN GmbH blacklist 
142.215.209.128/25
Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
209.236.109.189 ASN-FLEXENTIAL blacklist 
209.236.109.190 ASN-FLEXENTIAL blacklist 
202.58.142.250 Diligent Board Services Australia Pty Ltd blacklist 
202.58.142.251 Diligent Board Services Australia Pty Ltd blacklist 
202.58.140.250 Diligent Board Services Australia Pty Ltd blacklist 
202.58.140.251 Diligent Board Services Australia Pty Ltd blacklist 
89.187.106.61 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.187.106.62 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.21.6.61 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
89.21.6.62 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
149.97.158.154/31
Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
62.216.248.221 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
62.216.248.222 Equinix (EMEA) Acquisition Enterprises B.V. blacklist 
88.205.108.64/26
HKN GmbH blacklist 
52.169.26.47 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.113.102.113 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.127.193.239 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.104.186.102 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
51.104.187.101 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.54.98.173 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.52.209.236 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.67.179.11 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.82.222.250 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.92.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.107.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.100.0.0/15
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.102.0.0/16
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.103.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.47.0.0/17
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f400::/48
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403::/49
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:8000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:c000::/51
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:f000::/52
MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
213.198.99.210 NTT-LTD-2914 blacklist 
213.198.99.211 NTT-LTD-2914 blacklist 
213.198.99.216 NTT-LTD-2914 blacklist 
81.25.202.82 NTT-LTD-2914 blacklist 
185.238.12.20 GAS&COM AG blacklist 
185.238.12.21 GAS&COM AG blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: spf.dmgmori.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Additionally authorized IPv4 addresses

Explicit IPv4 addresses in the SPF record have been authorized to send

193.158.58.192/26
62.153.207.0/27
162.144.64.224
202.248.122.50
60.43.159.108
20.113.182.182
20.218.254.235
20.218.254.237
20.113.150.73
35.80.141.6
44.229.121.55

Additional external SPF records

We could find other records authorized in the SPF record

include:spf.boardbooks.com
v=spf1 ip4:74.217.54.250/31 ip4:49.255.152.93/31 ip4:74.121.167.29 ip4:74.121.167.30 ip4:88.205.100.160/27 ip4:213.9.75.59 ip4:213.9.75.60 ip4:142.215.209.128/25 ip4:209.236.109.189 ip4:209.236.109.190 ip4:202.58.142.250 ip4:202.58.142.251 ip4:202.58.140.250 ip4:202.58.140.251 ip4:89.187.106.61 ip4:89.187.106.62 ip4:89.21.6.61 ip4:89.21.6.62 ip4:149.97.158.154/31 ip4:62.216.248.221 ip4:62.216.248.222 ip4:88.205.108.64/26 ~all
ipv4:
74.217.54.250/31
ipv4:
49.255.152.93/31
ipv4:
74.121.167.29
ipv4:
74.121.167.30
ipv4:
88.205.100.160/27
ipv4:
213.9.75.59
ipv4:
213.9.75.60
ipv4:
142.215.209.128/25
ipv4:
209.236.109.189
ipv4:
209.236.109.190
ipv4:
202.58.142.250
ipv4:
202.58.142.251
ipv4:
202.58.140.250
ipv4:
202.58.140.251
ipv4:
89.187.106.61
ipv4:
89.187.106.62
ipv4:
89.21.6.61
ipv4:
89.21.6.62
ipv4:
149.97.158.154/31
ipv4:
62.216.248.221
ipv4:
62.216.248.222
ipv4:
88.205.108.64/26
include:spf.cloud.ci-solution.com
v=spf1 ip4:52.169.26.47 ip4:40.113.102.113 ip4:40.127.193.239 ip4:51.104.186.102 ip4:51.104.187.101 ip4:20.54.98.173 ip4:20.52.209.236 ip4:20.67.179.11 ip4:20.82.222.250 -all
ipv4:
52.169.26.47
ipv4:
40.113.102.113
ipv4:
40.127.193.239
ipv4:
51.104.186.102
ipv4:
51.104.187.101
ipv4:
20.54.98.173
ipv4:
20.52.209.236
ipv4:
20.67.179.11
ipv4:
20.82.222.250
include:spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/15 ip4:52.102.0.0/16 ip4:52.103.0.0/17 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/49 ip6:2a01:111:f403:8000::/51 ip6:2a01:111:f403:c000::/51 ip6:2a01:111:f403:f000::/52 -all
ipv4:
40.92.0.0/15
ipv4:
40.107.0.0/16
ipv4:
52.100.0.0/15
ipv4:
52.102.0.0/16
ipv4:
52.103.0.0/17
ipv4:
104.47.0.0/17
ipv6:
2a01:111:f400::/48
ipv6:
2a01:111:f403::/49
ipv6:
2a01:111:f403:8000::/51
ipv6:
2a01:111:f403:c000::/51
ipv6:
2a01:111:f403:f000::/52
include:spf.de.umantis.com
v=spf1 ip4:213.198.99.210 ip4:213.198.99.211 ip4:213.198.99.216 ip4:81.25.202.82 ip4:185.238.12.20 ip4:185.238.12.21 ~all
ipv4:
213.198.99.210
ipv4:
213.198.99.211
ipv4:
213.198.99.216
ipv4:
81.25.202.82
ipv4:
185.238.12.20
ipv4:
185.238.12.21

E-Mail handling

How should the checkHost() function of the e-mail server handle the e-mail? (syntax )

-all
Fail (non-compliant e-mails are rejected)

Will be forwarded to another SPF record?

There is no reference to any other SPF record

Are the server addresses allowed to send e-mails?

In the SPF entry the mechanism 'a' has not been set.

Additionally authorized A-records?

In addition to the A-Records stored in the DNS, we could not find any other records authorized in the SPF-Record.

Are the registered mail servers allowed to send e-mails?

In the SPF entry the mechanism 'mx' has not been set

Additionally authorized MX records

We could not find any other records authorized in the SPF record besides the MX records stored in the DNS

Additionally authorized IPv6 addresses

No explicit IPv6 addresses in the SPF record have been authorised to send

How is the sender informed?

The exp mechanism acts as a return to the sender if the IP address was not authorized to send and notify them. None was found.

PTR (obsolete mechanism)

The ptr mechanism is deprecated, slow and insecure and should not be used

PTR:

The ptr mechanism is deprecated, slow and insecure and should not be used

Authorize IP addresses with markers

When SPF is evaluated, macros can specifically authorize Ip addresses based on the request or connection of the user or client (RFC7208 )

Receiver address

analysis.ra-missing

Amount of reports

analysis.rp-missing

Report selection

analysis.rr-missing

Unknown mechanisms

No unknown mechanisms were found in the SPF record.

Recently performed SPF lookups

Server IP Address

We have determined the following IP address for the domain:

No domain specified

Reverse address

We have determined the following name for the server IP address:

No PTR record found

Free whitepaper

How secure is your domain?

  • Practical with many examples
  • the basics of domain risk management summarized in 20 pages
  • Checklist with 53 questions on 14 risk areas

Get a first impression of the risk potential in your company

⮩ Download "Domain Risk Management" for free
All offers are aimed at traders, not end consumers and do not include VAT.
© 2024 nicmanager.com.   All rights reserved.
nicmanager