SPF Check:
netceed.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
Summary of the SPF check

Does a valid SPF record exist?
An SPF record was found for the domain netceed.com.
The SPF record for netceed.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, 56 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 08.02.2025 at 06:07:34 clock.

Lookup for the domain:
netceed.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 netceed.com 

Nameserverset:
ns11.domaincontrol.com
ns12.domaincontrol.com
Canonical names of the domain
em1517.netceed.com u24612923.wl174.sendgrid.net em4943.netceed.com u24612990.wl241.sendgrid.net
Determined SPF record:
(u24612990.wl241.sendgrid.net)
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
75.2.70.75 AMAZON-02 blacklist 
99.83.190.102 AMAZON-02 blacklist 
52.101.166.0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.166.1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.166.2 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.101.164.0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:ca25:0:0:0:2 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:ca1e:0:0:0:0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:ca25:0:0:0:1 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
2a01:111:f403:ca25:0:0:0:0 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
24.199.235.55 TWC-11426-CAROLINAS blacklist 
37.228.156.127 dogado GmbH blacklist 
50.200.68.58 COMCAST-7922 blacklist 
52.232.64.209 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
81.148.206.228 British Telecommunications PLC blacklist 
81.169.145.64 Strato GmbH blacklist 
81.169.145.172 Strato GmbH blacklist 
85.233.120.230 KT-NET Communications GmbH blacklist 
88.198.176.152 Hetzner Online GmbH blacklist 
185.207.228.8 dogado GmbH blacklist 
185.221.38.18 team.blue Denmark A/S blacklist 
195.201.38.53 Hetzner Online GmbH blacklist 
212.88.144.50 VSE NET GmbH blacklist 
213.145.224.130 Ledl.net GmbH blacklist 
217.160.0.231 IONOS SE blacklist 
148.76.106.158 CABLE-NET-1 blacklist 
98.101.139.238 TWC-11426-CAROLINAS blacklist 
12.69.203.218 ATT-INTERNET4 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 
192.200.190.165/30
GOOGLE-CLOUD-PLATFORM blacklist 
104.195.80.16/28
- blacklist 
192.200.181.144/28
- blacklist 
63.141.144.128/28
- blacklist 
104.195.127.0/27
GOOGLE-CLOUD-PLATFORM blacklist 
205.201.128.0/20
THEROCKETSCIENCEGROUP blacklist 
198.2.128.0/18
THEROCKETSCIENCEGROUP blacklist 
148.105.8.0/21
THEROCKETSCIENCEGROUP blacklist 
149.72.39.242 SENDGRID blacklist 
149.72.27.104 SENDGRID blacklist 
13.74.137.176 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
52.138.216.130 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.114.221.220 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
40.113.3.253 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
23.100.56.64 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
137.116.240.241 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
13.74.144.83 MICROSOFT-CORP-MSN-AS-BLOCK blacklist 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: netceed.com

SPF record available?

We found an SPF record for the domain.

v=spf1

Are the server addresses allowed to send e-mails?

The mechanism 'a' was set in the SPF record. The following IP addresses are allowed to send

75.2.70.75
99.83.190.102

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

The mechanism 'mx' was set in the SPF entry. The following hosts are allowed to send

netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com
netceed-com.mail.protection.outlook.com

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf1.netceed.com
v=spf1 ip4:24.199.235.55 ip4:37.228.156.127 ip4:50.200.68.58 ip4:52.232.64.209 ip4:81.148.206.228 ip4:81.169.145.64 ip4:81.169.145.172 ip4:85.233.120.230 ip4:88.198.176.152 ip4:185.207.228.8 ip4:185.221.38.18 ip4:195.201.38.53 ip4:212.88.144.50 ip4:213.145.224.130 ip4:217.160.0.231 ip4:148.76.106.158 ip4:98.101.139.238 ip4:12.69.203.218 -all
ipv4:
24.199.235.55
ipv4:
37.228.156.127
ipv4:
50.200.68.58
ipv4:
52.232.64.209
ipv4:
81.148.206.228
ipv4:
81.169.145.64
ipv4:
81.169.145.172
ipv4:
85.233.120.230
ipv4:
88.198.176.152
ipv4:
185.207.228.8
ipv4:
185.221.38.18
ipv4:
195.201.38.53
ipv4:
212.88.144.50
ipv4:
213.145.224.130
ipv4:
217.160.0.231
ipv4:
148.76.106.158
ipv4:
98.101.139.238
ipv4:
12.69.203.218
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.bigcommerce.com
v=spf1 ip4:192.200.190.165/30 ip4:104.195.80.16/28 ip4:192.200.181.144/28 ip4:63.141.144.128/28 ip4:104.195.127.0/27
ipv4:
192.200.190.165/30
ipv4:
104.195.80.16/28
ipv4:
192.200.181.144/28
ipv4:
63.141.144.128/28
ipv4:
104.195.127.0/27
include:servers.mcsv.net
v=spf1 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 -all
ipv4:
205.201.128.0/20
ipv4:
198.2.128.0/18
ipv4:
148.105.8.0/21
include:em1517.netceed.com
v=spf1 ip4:149.72.39.242 -all
ipv4:
149.72.39.242
include:em4943.netceed.com
v=spf1 ip4:149.72.27.104 -all
ipv4:
149.72.27.104
include:spf-eu.emailsignatures365.com
v=spf1 ip4:13.74.137.176 ip4:52.138.216.130 ip4:40.114.221.220 ip4:40.113.3.253 ip4:23.100.56.64 ip4:137.116.240.241 ip4:13.74.144.83 -all
ipv4:
13.74.137.176
ipv4:
52.138.216.130
ipv4:
40.114.221.220
ipv4:
40.113.3.253
ipv4:
23.100.56.64
ipv4:
137.116.240.241
ipv4:
13.74.144.83

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 )

%{i}._spf.netceed.com

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

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.

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 IPv4 addresses

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

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

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:

aacb0a264e514dd48.awsglobalaccelerator.com

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.
© 2025 nicmanager.com.   All rights reserved.
nicmanager