Report for britishcouncil.org
NS Records at Parent Servers
We have successfully fetched domain's NS records from parent name server (
d0.org.afilias-nst.org.).
Domain NS records:
-
udns1.cscdns.net. TTL=3600
[NO GLUE4]
[NO GLUE6]
-
udns2.cscdns.uk. TTL=3600
[NO GLUE4]
[NO GLUE6]
Test ignored, name servers are located outside of current zone.
Name Servers Have A Records
OK.
Found A records for all name servers.
- udns1.cscdns.net. → 204.74.66.1
- udns2.cscdns.uk. → 204.74.111.1
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
OK.
Found AAAA records for all name servers.
- udns1.cscdns.net. → 2001:502:f3ff::201
- udns2.cscdns.uk. → 2001:502:4612::201
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Your name servers returned
2 NS records:
-
udns1.cscdns.net. TTL=86400
[NO GLUE4]
[NO GLUE6]
-
udns2.cscdns.uk. TTL=86400
[NO GLUE4]
[NO GLUE6]
All Name Servers Responded
OK.
All your name servers responded. We queried domain's records from all of your name servers and we received them successfully.
OK.
No differences found.
The glue provided by the parent name servers has to match
the data provided by the authoritative name servers.
OK.
Domain name servers are not allowing recursive queries.
On all name servers which acts as caching name servers recursive queries should be restricted to local networks.
Having open DNS servers can lead to abuses such as cache poisoning and DOS (denial of service) attacks.
Cache poisoning attacks allows under certain conditions to redirect legitimate web traffic,
email and other traffic to malicious hosts compromising security.
OK.
Domain has 2 name servers. Recommended number,
between 2 and 7 name servers (RFC 2182 recommends to have at
least 3 authoritative name servers for domains).
OK.
All your name servers reported identical NS records.
Each name server should return identical NS records.
Check for Lame Name servers
OK.
No lame name servers found. All of your name servers are configured to be either master or slave for your domain.
OK.
No private IPs found. Name servers using private IPs
can't be reached from the Internet causing DNS delays.
Name Servers Have A Records
OK.
Found A records for each name servers.
- udns1.cscdns.net. → 204.74.66.1
- udns2.cscdns.uk. → 204.74.111.1
To reach your name servers via IPv4 an A record is needed for each name server.
Name Servers Have AAAA Records
OK.
Found AAAA records for all name servers.
- udns1.cscdns.net. → 2001:502:f3ff::201
- udns2.cscdns.uk. → 2001:502:4612::201
To reach your name servers via IPv6 an AAAA record is needed for each name server.
Name Servers Have Valid Names
OK.
All names are valid.
Name server name should be a valid host name, no partial name or IP address.
Check for Stealth Name Servers
OK.
No stealth name servers found.
All name servers returned by domain name servers should be listed at parent servers.
Check for Missing Name Servers
OK.
No missing name servers found.
All name servers returned by the parent name servers should have an NS record at your name servers.
OK.
No CNAMEs found in NS records.
RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)
and must not point to any CNAME records.
RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)
it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with
NS and MX records.
Despite this restrictions, there are many working configuration using CNAME with
NS and MX records.
OK.
All name servers are allowing TCP connections.
When response to a DNS query exceeds 512 bytes, TCP is negotiated
and used, all name servers should allow TCP connections (port 53).
Name Servers Distributed on Multiple Networks
OK.
Name servers are dispersed on 2
different C class networks:
-
204.74.111.0/24:
-
204.74.66.0/24:
Name servers should be dispersed (topologically and geographically)
across the Internet to avoid risk of single point of failure (RFC 2182).
Name Servers Distributed on Multiple ASNs
OK.
Name servers are dispersed on 9
different Autonomous Systems:
-
AS397213:
-
AS397215:
-
AS397218:
-
AS397220:
-
AS397224:
-
AS397231:
- udns1.cscdns.net.
- udns2.cscdns.uk.
-
AS397232:
-
AS397233:
-
AS397235:
Name servers should be dispersed (topologically and geographically)
across the Internet to avoid risk of single point of failure (RFC 2182).
OK.
Name servers software versions are not exposed:
- 2001:502:4612::201: "UltraDNS Nameserver"
- 2001:502:f3ff::201: "UltraDNS Nameserver"
- 204.74.111.1: "UltraDNS Nameserver"
- 204.74.66.1: "UltraDNS Nameserver"
Exposing name server's versions may be risky, when a new vulnerability is found
your name servers may be automatically exploited by
script kiddies
until you patch the system.
Learn how to hide version.
Domain SOA Record:
- Primary nameserver: udns1.cscdns.net.
- Hostmaster (e-mail): hostmaster.cscdns.net.
- Serial: 2018075654
- Refresh: 10800
- Retry: 1800
- Expire: 3600000
- Minimum TTL: 300
Name Servers Agreement on Serial Number
OK.
All name servers (2) have the same
serial number [2018075654].
Having different serials on your name servers may show inconsistencies between name servers
configuration (multiple masters), or communication errors (ACL and firewall issues).
OK.
Serial number format OK [2018075654].
Your serial number is following general convention for
serial number YYYYMMDDnn, where YYYY is four-digit year
number, MM is the month, DD is the day and nn is the
sequence number in case zone file is updated more
than once per day.
OK.
Primary name server is udns1.cscdns.net. and is listed at the parent name servers.
The MNAME field defines the Primary Master name server for the zone,
this name server should be found in your NS records.
OK.
Contact email for DNS problems is hostmaster@cscdns.net. (hostmaster.cscdns.net.).
RNAME field defines an administrative email for your zone. RFC2142 recommends using hostmaster
e-mail for this purpose, but any valid e-mail address can be used.
OK.
Refresh interval is 10800.
Recommended values [1200 .. 43200] (20 min ... 12 hours).
Refresh field from SOA record determines how quickly zone changes are propagated from master to slave.
OK.
Retry interval is 1800.
Recommended values [120 .. 7200] (2 minutes .. 2 hours).
Retry field from SOA record defines how often slave should retry contacting master if connection to master failed during refresh.
WARNING:
Expire interval is 3600000.
Recommended values [604800 .. 1209600] (1 week ... 2 weeks).
Expiry defines zone expiration time in seconds after which slave must re-validate zone file,
if contacting master fails then slave will stop responding to any queries.
WARNING:
Minimum TTL value is 300.
Recommended values [3600 .. 86400] (1 hour ... 1 day).
Minimum TTL was redefined in RFC 2308, now it defines the period of time used by slaves
to cache negative responses.
Your name servers returned
1 MX records.
Your MX records sorted by priority (lower numbers have higher priority):
-
10 britishcouncil-org.mail.protection.outlook.com. TTL=86400
OK.
All name servers returned identical MX records.
Mail Servers Have A Records
OK.
Found A records for all mail servers.
- britishcouncil-org.mail.protection.outlook.com. → 52.101.73.12, 52.101.68.8, 52.101.73.30, 52.101.68.36
To reach your mail servers via IPv4 an A record is needed for each mail server.
Mail Servers Have AAAA Records
NOTICE:
While reading domain NS records at parent mail servers,
we found mail servers without AAAA records.
- britishcouncil-org.mail.protection.outlook.com. → ?
To reach your mail servers via IPv6 an AAAA record is needed for each mail server.
Reverse Entries for MX records
OK.
All mail servers have reverse DNS entries configured correctly.
|
Server |
IP |
PTR (Reverse) |
IPs |
|
britishcouncil-org.mail.protection.outlook.com. |
52.101.73.12 |
mail-am4pr0401cu00104.inbound.protection.outlook.com. |
52.101.73.12 |
|
britishcouncil-org.mail.protection.outlook.com. |
52.101.68.8 |
mail-du0pr03cu00100.inbound.protection.outlook.com. |
52.101.68.8 |
|
britishcouncil-org.mail.protection.outlook.com. |
52.101.73.30 |
mail-am7pr05cu00306.inbound.protection.outlook.com. |
52.101.73.30 |
|
britishcouncil-org.mail.protection.outlook.com. |
52.101.68.36 |
mail-db5pr02cu00104.inbound.protection.outlook.com. |
52.101.68.36 |
All mail servers should have a reverse DNS (PTR) entry for
each IP address (RFC 1912). Missing reverse DNS entries will
make many mail servers to reject your e-mails or mark them
as SPAM.
All IP's reverse DNS entries should resolve back to
IP address (IP → PTR → IP).
Many mail servers are configured to reject e-mails from
IPs with inconsistent reverse DNS configuration.
Check MX Records for Invalid Chars
OK.
No invalid characters found.
Name field from MX records should be a valid host name.
Check MX Records IPs are Public
OK.
No private IPs found.
Mail servers using private IPs can't be reached from the Internet causing mail delivery delays.
Check MX Records for Duplicates
OK.
No MX records duplicates (same IP addresses) found.
Although technically valid, duplicate MX records have no benefits and can cause confusion.
Only Host Names in MX Records
OK.
No IPs found in MX records.
IP addresses are not allowed in MX records, only host names.
OK.
No CNAMEs found in MX records.
RFC 2181, section 10.3 says that host name must map directly to one or more address record (A or AAAA)
and must not point to any CNAME records.
RFC 1034, section 3.6.2 says if a name appears in the right-hand side of RR (Resource Record)
it should not appear in the left-hand name of CNAME RR, thus CNAME records should not be used with
NS and MX records.
Despite this restrictions, there are many working configuration using CNAME with
NS and MX records.
OK.
Mail servers IPs are not blacklisted.
Check Google Apps Settings
Test ignored, domain is not using Google Apps.
OK.
Successfully connected to all mail servers.
To receive emails, mail servers should allow TCP connections on port 25.
NOTICE:
I've found differences between mail server host names
and greeting host name. The following mail servers claims
to be other hosts (reverse DNS checks may be wrong):
- britishcouncil-org.mail.protection.outlook.com. → am4pepf00027a68.mail.protection.outlook.com
Accepts Postmaster Address
OK.
All mail servers are accepting emails to
postmaster@britishcouncil.org address:
RFC 822, RFC 1123 and RFC 2821 requires that all domain's mail servers should accept e-mails to postmaster.
To be compliant you can create an alias and forward all postmaster's e-mails to a valid mailbox.
OK.
All mail servers are accepting emails to
abuse@britishcouncil.org address:
OK.
Found SPF record:
- q85r27f4gpcl3lq9ntfkjdlk99syzggn
- amazonses:MMLbONb+7wkBjpWs0yPcSfPEG1LZO0AZ1D8dX1TDENc=
- t5o0g46t4vjcgo1mqcrn3pf4nt
- pardot734493=e69544bcacfb96122123974d3e7e180dcc7a2c5a4cd9cb82b00af0a06dfa68c1
- successfactors-site-verification=YWVhMjBjOWFiNmVkNmE2YTYyMTE4YTAyOTJhODNlNDA4MDk1N2VhODhhNzc4YjFhYThkYjA5OTc2MWQ3ZjNkYw==
- nutobudlqgqaq8ub2044tg2tqp
- v=spf1 a ip4:146.88.16.128 ip4:146.88.16.129 ip4:146.88.16.130 ip4:146.88.16.131 ip4:146.88.16.132 ip4:146.88.16.133 ip4:146.88.16.134 ip4:146.88.16.135 ip4:27.126.146.0/24 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:203.55.21.0/24 ip4:204.75.142.0/24
- ip4:103.28.41.11 ip4:103.28.41.12 ip4:103.28.41.253 ip4:103.28.41.254 ip4:213.52.186.141 ip4:213.52.186.142 ip4:188.95.96.121 ip4:115.112.50.0/24 ip4:14.140.248.0/24 ip4:14.142.107.0/24 ip4:45.114.76.0/24 ip4:45.114.77.0/24 ip4:52.209.23.163
- ip4:34.241.194.188 ip4:81.128.176.3 ip4:163.164.224.226 ip4:149.72.255.210 ip4:5.61.115.80/28 ip4:103.28.42.0/24 ip4:146.88.28.0/24 ip4:203.55.21.0/24 ip4:204.75.142.0/24 ip4:51.144.186.223 ip4:51.105.207.247 ip4:213.52.186.141/32 ip4:213.52.186.142/32
- ip4:213.52.186.100/32 ip4:213.52.186.101/32 ip4:52.18.23.154 ip4:52.18.43.91 ip4:52.17.241.150 ip4:52.18.16.92 ip4:52.18.25.116 ip4:52.18.36.148 ip4:206.16.62.8 ip4:12.129.29.148 ip4:12.129.29.149 ip4:12.129.29.143 ip4:12.129.29.166 ip4:84.14.175.234
- ip4:199.108.17.100 ip4:199.108.17.115 ip4:12.129.29.150 ip4:12.129.29.202 ip4:66.45.118.65 ip4:52.80.13.198 ip4:52.80.1.243 ip4:155.56.208.100/30 ip4:157.133.97.216/30 ip4:169.145.66.70/31 ip4:169.145.66.72/31 ip4:87.253.232.0/21 ip4:185.189.236.0/22
- ip4:185.211.120.0/22 ip4:185.250.236.0/22 ip4:3.93.157.0/24 ip4:3.210.190.0/24 ip4:18.208.124.128/25 ip4:54.174.52.0/24 ip4:54.174.53.128/30 ip4:54.174.57.0/24 ip4:54.174.59.0/24 ip4:54.174.60.0/23 ip4:54.174.63.0/24 ip4:139.180.17.0/24
- ip4:143.244.80.0/20 ip4:158.247.16.0/20 ip4:35.214.208.81 ip4:35.214.183.81 ip4:35.214.213.218 ip4:35.214.212.238 ip4:198.21.6.21 ip4:198.61.254.23 ip4:52.70.180.81 ip4:103.170.105.192 ip4:103.170.105.182 ip4:103.170.105.180 ip4:103.8.238.88
- ip4:103.219.238.161 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:167.89.0.0/17 ip4:27.126.146.0/24 ip4:103.28.42.0/24 ip4:146.88.28.0/24
- ip4:203.55.21.0/24 ip4:204.75.142.0/24 include:nw008.com include:amazonses.com include:spf.protection.outlook.com include:spf.eventsforce.net include:_spf.salesforce.com include:aspmx.pardot.com -all
- have-i-been-pwned-verification=58272196a0695f839fe50a753a12ad31
- MS=ms20905763
- google-site-verification=UgDP8kByjx7CcNfnmDAaWJFq7QdAO0q_4NGdVW9WkYs
- vunl8jav4tviuh40jjk7bodpj6
- facebook-domain-verification=3mxrzjuz6kenhn2myv0ys6494p0xt0
- docusign=41d69863-069f-4e07-9119-44dbf92b16f9
- 2ajvpqrb2iisu3vtea05f9mmvk
- atlassian-domain-verification=33ikTgnfsuT67cLnfuaf17SCEpiEB8P1hGm74dZxq5KcGh/L67sxcPHqtEnB43Fi
- MS=ms98019366
- canva-site-verification=NdTKN00yKWa7prcGdMomOA
- zgc4kx48kswsv0t79yk21c0srtp99y47
- facebook-domain-verification=qp3a35ck90ejfz2jsvydt74ovbcmlk
- facebook-domain-verification=rpq0q2rzi1c8lgp481kr238mt9qxmr
- _globalsign-domain-verification=Iiihy-iv_vLdlIMtHvh-aCdqO2T53oCoknhW44njXn
- pq7hyngm5mwj5fppjnd6mg8nn07d75jb
- atlassian-domain-verification=oIwQZaz/MRtMsmoTYe5W6WLa1J3fT6UJkyvv2JrBnFsQ/wyfiNSdMcnzqZ7GDHGP
- pardot734493=67935687422f2454fe052217ac76ab63ab59fc40e4134c2fa9b5a3268c472be9
- google-site-verification=_u_fwHAdWJbzxQb-ezGy-dUesA564Gppsvip4G8a7A8
- 12B9-B7AC-317F-AED7-FAD9-0A42-E45F-D313
- facebook-domain-verification=71tbmms7av1qecz81zzaelm6fx9opy
- 7s9y18hclbnxm7yc7435g96bqytc7hwg
- MS=8224EDAEE029157FC7A12ED206027FC27E59B2E1
- google-site-verification=LIiYwDJxV02_6nQXvCmtpWhUq1BDqLCcEeRFRe72nEE
- _globalsign-domain-verification=lQgTOD8dWU_8nHyzjHGJ39ncrI45HenuNvKKTckDhn
- _globalsign-domain-verification=-awtonA3izZim7M9dNMwrH07WjvKC5se353wYCAliP
- amazonses:2OVofWfsKIZZF/83yrjW6275PmjifFAdrkNmWj9bgYk=
- docusign=9fcfefe4-8429-4547-9d60-3db6745bf374
- mandrill_verify.zNeiG-fMxD_LFaWXIeGcnQ
- google-site-verification=2gaaYLJS1Yg09dGBEJbIXolkPDKZMLDshodUb_ZMK4A
SPF
(Sender Policy Framework) record is designed to prevent e-mail spoofing.
Typical SPF record would be:
v=spf1 a mx ~all
or
v=spf1 a mx include:_spf.google.com ~all if you are using Google Apps.
OK.
Name servers returned identical TXT records.
Only SPF records are compared, all name servers should return identical SPF records.
No SPF type records found.
All name servers should return identical SPF records.
FAIL:
Domain doesn't have DMARC record.
The DMARC
uses DKIM keys published in the DNS or IP addresses specified in the SPF
record to authenticate emails to protect domain from fraudulent emails.
You can specify a policy how to deal with emails which fails authentication.
A typical policy would be to reject, this applies to the domain and
all its subdomains without an explicit policy.
The DMARC policy has precedence over SPF policy.
If you are more conservative, you can start with quarantine.
Example DMARC record:
v=DMARC1; p=quarantine
The authenticated emails will be delivered in the Inbox and others in the Spam/Junk folder.
OK.
Domain
britishcouncil.org. resolves to:
- 23.46.72.47
Domain Name IPs are Public
OK.
No private IPs found for britishcouncil.org..
Web servers using private IPs can't be reached from the Internet.
OK.
Domain
www.britishcouncil.org. resolves to:
- 2.17.5.13
OK.
No private IPs found for www.britishcouncil.org..
Web servers using private IPs can't be reached from the Internet.
Report completed in 1.43 seconds.
Recent reports:
mail-office.eu
mail-office.eu
traderepublic.com
themidoceanclub.com
cpscontabil.com.br