SPF Check:
spf.ecbeing.co.jp

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.ecbeing.co.jp 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.ecbeing.co.jp.
The SPF record for spf.ecbeing.co.jp is valid.
The syntax check of the SPF record shows no obvious errors.

Which IP-s are legitimate to send emails?
In total, 46 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 14.11.2024 at 23:47:15 clock.

Lookup for the domain:
spf.ecbeing.co.jp
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.ecbeing.co.jp 

Nameserverset:
ns-1704.awsdns-21.co.uk
ns-879.awsdns-45.net
ns-472.awsdns-59.com
ns-1416.awsdns-49.org
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
203.183.103.0/24
IDC Frontier Inc. blacklist 
20.78.44.251 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
202.32.114.0/23
Internet Initiative Japan Inc. blacklist 
163.49.12.0/24
Internet Initiative Japan Inc. blacklist 
163.49.25.0/24
Internet Initiative Japan Inc. blacklist 
210.148.197.0/24
Internet Initiative Japan Inc. blacklist 
52.156.52.96 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
138.91.5.52 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.188.6.233 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.198.108.90 AMAZON-02 blacklist 
3.113.195.4 AMAZON-02 blacklist 
52.246.167.54 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.246.186.246 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.246.167.189 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.78.64.251 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.156.57.7 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.243.44.38 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.102.72.233 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
210.152.91.64/26
IDC Frontier Inc. blacklist 
13.113.144.112 AMAZON-02 blacklist 
20.89.56.151 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.89.57.192 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.188.9.180 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.188.11.182 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.188.31.56 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.78.31.66 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.89.97.86 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
20.48.29.212 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
211.10.12.192/26
IDC Frontier Inc. blacklist 
202.218.125.64/26
IDC Frontier Inc. blacklist 
202.218.77.128/25
IDC Frontier Inc. blacklist 
203.183.233.128/25
IDC Frontier Inc. blacklist 
203.183.236.0/24
IDC Frontier Inc. blacklist 
202.234.6.128/25
IDC Frontier Inc. blacklist 
61.195.171.0/27
IDC Frontier Inc. blacklist 
203.183.137.128/25
IDC Frontier Inc. blacklist 
210.129.210.0/25
IDC Frontier Inc. blacklist 
203.183.50.128/25
IDC Frontier Inc. blacklist 
202.230.13.128/25
IDC Frontier Inc. blacklist 
202.218.77.0/25
IDC Frontier Inc. blacklist 
20.37.121.5 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.106.28 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.111.94 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.74.70.135 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
104.215.9.18 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
202.32.58.0/24
Internet Initiative Japan Inc. blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: spf.ecbeing.co.jp

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

203.183.103.0/24
20.78.44.251
202.32.114.0/23
163.49.12.0/24
163.49.25.0/24
210.148.197.0/24
52.156.52.96
138.91.5.52
20.188.6.233
52.198.108.90
3.113.195.4
52.246.167.54
52.246.186.246
52.246.167.189
13.78.64.251
52.156.57.7
52.243.44.38
23.102.72.233
210.152.91.64/26
13.113.144.112
20.89.56.151
20.89.57.192
20.188.9.180
20.188.11.182
20.188.31.56
13.78.31.66
20.89.97.86
20.48.29.212
211.10.12.192/26
202.218.125.64/26
202.218.77.128/25
203.183.233.128/25
203.183.236.0/24
202.234.6.128/25
61.195.171.0/27
203.183.137.128/25
210.129.210.0/25
203.183.50.128/25
202.230.13.128/25
202.218.77.0/25
20.37.121.5
23.100.106.28
23.100.111.94
40.74.70.135
104.215.9.18
202.32.58.0/24

E-Mail handling

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

~all
SoftFail (non-compliant e-mails are accepted but marked)

Unknown mechanisms

Unknown mechanisms were found in the SPF record


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

Additional external SPF records

We could not find any other records authorized in SPF-Record

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

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