SPF Check:
bankofsingapore.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 bankofsingapore.com.
The SPF record for bankofsingapore.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, 40 IP address(es) were authorized by the SPF record to send emails.

The SPF record analysis was performed on 28.08.2025 at 16:13:12 clock.

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

Nameserverset:
secdns.starhub.net.sg
secdns2.starhub.net.sg
a5-66.akam.net
a11-67.akam.net
a1-177.akam.net
a16-64.akam.net
a10-66.akam.net
a24-65.akam.net
Determined SPF record:
Legitimated IP addresses:
IP Provider / ASN DNSBL-Check
203.126.194.83 SingNet blacklist 
203.116.27.83 StarHub Ltd blacklist 
203.116.27.82 StarHub Ltd blacklist 
203.126.194.82 SingNet blacklist 
45.60.124.168 INCAPSULA blacklist 
45.60.126.168 INCAPSULA blacklist 
203.117.19.195 StarHub Ltd blacklist 
203.127.116.86 SingNet blacklist 
111.223.119.198 StarHub Ltd blacklist 
128.106.3.8 SingNet blacklist 
128.106.3.38 SingNet blacklist 
61.8.223.68 StarHub Ltd blacklist 
203.115.204.13 Arcnet NTT MSC ISP blacklist 
203.125.118.182 SingNet blacklist 
61.8.195.182 StarHub Ltd blacklist 
58.26.21.150 TM TECHNOLOGY SERVICES SDN. BHD. blacklist 
203.126.194.98 SingNet blacklist 
203.116.27.98 StarHub Ltd blacklist 
203.126.194.83 SingNet blacklist 
203.126.194.82 SingNet blacklist 
203.116.27.83 StarHub Ltd blacklist 
203.116.27.82 StarHub Ltd blacklist 
113.23.173.43 Extreme Broadband - Total Broadband Experience blacklist 
113.23.173.64 Extreme Broadband - Total Broadband Experience blacklist 
203.126.154.179 SingNet blacklist 
203.116.43.227 StarHub Ltd blacklist 
129.41.222.143 AMAZON-02 blacklist 
208.85.50.136 AMAZON-AES blacklist 
208.73.7.251 AMAZON-02 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 
SPF-Syntax Check:
Analysis result of the SPF record for the domain: bankofsingapore.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

45.60.124.168
45.60.126.168

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

raffles.bankofsingapore.com
raffles.bankofsingapore.com
stamford.bankofsingapore.com
stamford.bankofsingapore.com

Additionally authorized IPv4 addresses

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

129.41.222.143
208.85.50.136
208.73.7.251

Additional external SPF records

We could find other records authorized in the SPF record

include:_spf2.bankofsingapore.com
v=spf1 +ip4:203.117.19.195 ip4:203.127.116.86 ip4:111.223.119.198 ip4:128.106.3.8 ip4:128.106.3.38 ip4:61.8.223.68 ip4:203.115.204.13 ip4:203.125.118.182 ip4:61.8.195.182 ip4:58.26.21.150 ip4:203.126.194.98 ip4:203.116.27.98 ~all
ipv4:
203.117.19.195
ipv4:
203.127.116.86
ipv4:
111.223.119.198
ipv4:
128.106.3.8
ipv4:
128.106.3.38
ipv4:
61.8.223.68
ipv4:
203.115.204.13
ipv4:
203.125.118.182
ipv4:
61.8.195.182
ipv4:
58.26.21.150
ipv4:
203.126.194.98
ipv4:
203.116.27.98
include:_spf3.bankofsingapore.com
v=spf1 +ip4:203.126.194.83 ip4:203.126.194.82 ip4:203.116.27.83 ip4:203.116.27.82 ip4:113.23.173.43 ip4:113.23.173.64 ip4:203.126.154.179 ip4:203.116.43.227 -all
ipv4:
203.126.194.83
ipv4:
203.126.194.82
ipv4:
203.116.27.83
ipv4:
203.116.27.82
ipv4:
113.23.173.43
ipv4:
113.23.173.64
ipv4:
203.126.154.179
ipv4:
203.116.43.227
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

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 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:

45.60.126.168

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