Web Security Overview
Warning
HTTPS

Web sites need to use encryption to help their visitors know they're in the right place, as well as provide confidentiality and content integrity. Sites that don't support HTTPS may expose sensitive data and have their pages modified and subverted.
There are issues with this site's HTTPS configuration.

For all sites VERY IMPORTANT medium EFFORT
Supported and well configured
HTTPS Redirection

To deploy HTTPS properly, web sites must redirect all unsafe (plaintext) traffic to the encrypted variant. This approach ensures that no sensitive data is exposed and that further security technologies can be activated.

For all sites VERY IMPORTANT low EFFORT
Not supported
HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) is an HTTPS extension that instructs browsers to remember sites that use encryption and enforce strict security requirements. Without HSTS, active network attacks are easy to carry out.

For important sites VERY IMPORTANT medium EFFORT
Not supported
HSTS Preloaded

HSTS Preloading is informing browsers in advance about a site's use of HSTS, which means that strict security can be enforced even on the first visit. This approach provides best HTTPS security available today.

For important sites VERY IMPORTANT medium EFFORT
Not supported
Content Security Policy

Content Security Policy (CSP) is an additional security layer that enables web sites to control browser behavior, creating a safety net that can counter attacks such as cross-site scripting.

For important sites IMPORTANT high EFFORT
Email Security Overview
Not supported
STARTTLS

All hosts that receive email need encryption to ensure confidentiality of email messages. Email servers thus need to support STARTTLS, as well as provide decent TLS configuration and correct certificates.

For all sites VERY IMPORTANT low EFFORT
Supported and well configured
SPF

Sender Policy Framework (SPF) enables organizations to designate servers that are allowed to send email messages on their behalf. With SPF in place, spam is easier to identify.

For important sites IMPORTANT low EFFORT
Not supported
DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism that allows organizations to specify how unauthenticated email (identified using SPF and DKIM) should be handled.

For important sites IMPORTANT low EFFORT

Name Server Configuration

Correctly functioning name servers are necessary to hold and distribute information that's necessary for your domain name to operate correctly. Examples include converting names to IP addresses, determining where email should go, and so on. More recently, the DNS is being used to communicate email and other security policies.

Test passed
Everything seems to be well configured. Well done.

DNS Configuration

These are the results of individual DNS queries against your nameserver for each resource record type.

Name TTL Type Data
yahoo.co.jp.     300 A 183.79.135.206            
yahoo.co.jp.     300 A 182.22.59.229            
www.yahoo.co.jp.     900 CNAME edge12.g.yimg.jp.            
edge12.g.yimg.jp.     60 A 183.79.219.252            
yahoo.co.jp.     900 CAA 0 issue "globalsign.com"            
yahoo.co.jp.     900 CAA 0 issue "cybertrust.ne.jp"            
yahoo.co.jp.     900 CAA 0 issue "digicert.com;cansignhttpexchanges=yes"            
yahoo.co.jp.     900 CAA 0 iodef "mailto:nic-admin@mail.yahoo.co.jp"            
yahoo.co.jp.     900 MX 10 mx1.mail.yahoo.co.jp.            
yahoo.co.jp.     900 MX 10 mx3.mail.yahoo.co.jp.            
yahoo.co.jp.     900 MX 10 mx5.mail.yahoo.co.jp.            
yahoo.co.jp.     900 MX 10 mx2.mail.yahoo.co.jp.            
yahoo.co.jp.     900 TXT v=spf1 include:spf.yahoo.co.jp ~all            
yahoo.co.jp.     900 TXT google-site-verification=GvbYgNin-mY73VbS4IJK2D8nI3tHEf2NpRdy76VYqBU            
_dmarc.yahoo.co.jp.     900 TXT v=DMARC1; p=none; rua=mailto:ymail_dmarc_report@yahoo.co.jp            
yahoo.co.jp.     900 NS ns01.yahoo.co.jp.            
yahoo.co.jp.     900 NS ns12.yahoo.co.jp.            
yahoo.co.jp.     900 NS ns02.yahoo.co.jp.            
yahoo.co.jp.     900 NS ns11.yahoo.co.jp.            
yahoo.co.jp.     900 SOA yahoo.co.jp. postmaster.yahoo.co.jp. 2106180010 1800 900 86400 900            

DNSSEC

DNSSEC is an extension of the DNS protocol that provides cryptographic assurance of the authenticity and integrity of responses; it's intended as a defense against network attackers who are able to manipulate DNS to redirect their victims to servers of their choice. DNSSEC is controversial, with the industry split largely between those who think it's essential and those who believe that it's problematic and unnecessary.

Feature not implemented or disabled
Your server doesn't support this feature.

Useful DNSSEC Tools

Certification Authority Authorization

CAA (RFC 8659) is a new standard that allows domain name owners to restrict which CAs are allowed to issue certificates for their domains. This can help to reduce the chance of misissuance, either accidentally or maliciously. In September 2017, CAA became mandatory for CAs to implement.

Test passed
Everything seems to be well configured. Well done.

CAA Policy Information

The DNS hostname where this policy is located.Policy host yahoo.co.jp
The iodef property specifies a means of reporting certificate
issue requests or cases of certificate issue for the corresponding
domain that violate the security policy of the issuer or the domain
name holder.
iodef
mailto:nic-admin@mail.yahoo.co.jp  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
globalsign.com  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
digicert.com;cansignhttpexchanges=yes  flags: 0
The issue property tag is used to request that certificate
issuers perform CAA issue restriction processing for the domain
and to grant authorization to specific certificate issuers.
issue
cybertrust.ne.jp  flags: 0

Analysis

Good
CAA policy found
Good. This domain name uses CAA to restrict which CAs are allowed to issue certificates for it.
Good
Policy uses reporting
Great. This policy uses reporting, which means that your contact information is available should someone need to contact you about a CAA violation. Do note that you're not guaranteed to be notified, given that CAs generally don't support notifications yet.

Email (SMTP)

An internet hostname can be served by zero or more mail servers, as specified by MX (mail exchange) DNS resource records. Each server can further resolve to multiple IP addresses, for example to handle IPv4 and IPv6 clients. Thus, in practice, hosts that wish to receive email reliably are supported by many endpoint.

Test failed
We've detected serious problems that require your immediate attention.
Server Preference Operational STARTTLS TLS PKI DNSSEC DANE
mx5.mail.yahoo.co.jp
202.93.78.239
PTR: mtagw0008.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0043.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0043.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx5.mail.yahoo.co.jp
202.93.78.240
PTR: mtagw0007.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0041.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0041.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx5.mail.yahoo.co.jp
124.83.142.248
PTR: mtagw7007.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7037.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7037.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx5.mail.yahoo.co.jp
124.83.142.247
PTR: mtagw7008.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7043.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7043.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx3.mail.yahoo.co.jp
202.93.78.241
PTR: mtagw0006.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0031.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0031.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx3.mail.yahoo.co.jp
124.83.142.250
PTR: mtagw7005.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7028.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7028.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx3.mail.yahoo.co.jp
124.83.142.249
PTR: mtagw7006.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7034.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7034.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx3.mail.yahoo.co.jp
202.93.78.242
PTR: mtagw0005.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0029.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0029.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx2.mail.yahoo.co.jp
124.83.142.118
PTR: mtagw7004.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7022.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7022.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx2.mail.yahoo.co.jp
124.83.142.119
PTR: mtagw7003.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7014.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7014.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx2.mail.yahoo.co.jp
202.93.77.239
PTR: mtagw0003.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0017.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0017.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx2.mail.yahoo.co.jp
202.93.77.238
PTR: mtagw0004.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0023.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0023.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx1.mail.yahoo.co.jp
202.93.77.240
PTR: mtagw0002.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0008.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0008.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx1.mail.yahoo.co.jp
124.83.142.124
PTR: mtagw7001.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7004.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7004.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx1.mail.yahoo.co.jp
202.93.77.241
PTR: mtagw0001.mail.vip.otm.ynwp.yahoo.co.jp
10
220 mtagw0003.mail.otm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw0003.mail.otm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.
mx1.mail.yahoo.co.jp
124.83.142.123
PTR: mtagw7002.mail.vip.djm.ynwp.yahoo.co.jp
10
220 mtagw7011.mail.djm.ynwp.yahoo.co.jp ESMTP ready

EHLO outbound.hardenize.com
250-mtagw7011.mail.djm.ynwp.yahoo.co.jp
250-PIPELINING
250-8BITMIME
250 SIZE 20480000

QUIT
221 2.0.0 Bye
Doesn't support STARTTLS. Not applicable,
requires STARTTLS.
Not applicable,
requires TLS.
Not supported. Not applicable,
requires TLS.

Analysis

Notice
Some SMTP server assessments contain partial information
Comprehensive TLS assessments require many connections, which is exactly what many SMTP servers don't like. We implement a two-tier assessment approach. To give you some results as fast as possible, we perform shallow assessments that use only one connection per SMTP server. We then have a background process that performs complete assessments slowly, trying to accommodate each server individually. The results presented here contain partial information. If you come back later we may be able to provide complete assessment resuls.

Email TLS (SMTP)

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test failed
We've detected serious problems that require your immediate attention.

Analysis

Error
No support for STARTTLS
One or more servers lack support for STARTTLS, which means that they do not support email encryption at all.

Email Certificates (SMTP)

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Feature not implemented or disabled
Your server doesn't support this feature.

Email DANE (SMTP)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not implemented or disabled
Your server doesn't support this feature.

SPF

Sender Policy Framework (SPF) is a protocol that allows domain name owners to control which internet hosts are allowed to send email on their behalf. This simple mechanism can be used to reduce the effect of email spoofing and cut down on spam.

Test passed
Everything seems to be well configured. Well done.

SPF Policy Information Main policy

Host where this policy is located.Location yahoo.co.jp
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf.yahoo.co.jp
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

Analysis

Info
SPF policy found

Policy text: v=spf1 include:spf.yahoo.co.jp ~all

Location: yahoo.co.jp

Good
SPF policy is valid
Good. Your SPF policy is valid.
Good
Policy DNS lookups under limit
Good. Your policy stays under the limit of up to 10 DNS queries. The SPF specification Section 4.6.4. requires implementations to limit the total number of DNS queries. Policies that exceed the limit should not be used and may not work in practice.

Lookups: 7

SPF Policy Information Included policy

Host where this policy is located.Location spf.yahoo.co.jp
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf01.yahoo.co.jp
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf02.yahoo.co.jp
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
spf03.yahoo.co.jp
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
bulk-spf.yahoo.co.jp
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location spf01.yahoo.co.jp
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
114.110.61.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.56.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.100.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.106.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.108.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.110.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.145.0/24
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location spf02.yahoo.co.jp
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.12.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.16.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
202.93.77.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
202.93.78.0/24
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location spf03.yahoo.co.jp
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.37.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.46.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.90.0/23
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.109.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.124.0/24
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location bulk-spf.yahoo.co.jp
SPF version used by this policy.v spf1
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
bulk-spf-east.yahoo.co.jp
Evaluates SPF policy specified in another DNS location. This
directive is typically used to allow hosts controlled by
another organization.
include
bulk-spf-west.yahoo.co.jp
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location bulk-spf-east.yahoo.co.jp
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
203.216.234.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
203.216.240.0/24
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
118.151.232.188/30
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
203.216.249.0/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
118.151.229.192/26
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
118.151.229.109
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
118.151.229.110
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.32.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
118.151.224.0/19
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
182.22.20.0/26
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

SPF Policy Information Included policy

Host where this policy is located.Location bulk-spf-west.yahoo.co.jp
SPF version used by this policy.v spf1
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
124.83.128.0/17
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
114.111.64.0/18
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
114.110.48.0/20
This mechanism tests whether the IP address being
tested is contained within a given IPv4 network.
ip4
183.79.0.0/16
This policy element always matches. It's normally used
at the end of a policy to specify the handling of hosts
that don't match earlier mechanisms.
~all

DMARC

Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling.

Feature not implemented or disabled
Your server doesn't support this feature.

DMARC Policy Information

The location from which we obtained this policy.Policy location _dmarc.yahoo.co.jp
DMARC version used by this policy.v DMARC1
Indicates the policy to be enacted by the receiver at
the request of the domain owner. Possible values are:
none, quarantine, and reject.
p
none
Addresses to which aggregate feedback is to be sent.rua mailto:ymail_dmarc_report@yahoo.co.jp

Analysis

Info
DMARC policy found

Policy: v=DMARC1; p=none; rua=mailto:ymail_dmarc_report@yahoo.co.jp

Host: _dmarc.yahoo.co.jp

Good
Policy is valid
Good. You have a valid DMARC policy.
Powerup!
Activate DMARC policy
Although syntactically valid, your DMARC policy is effectively disabled. An effective policy must set the value of the 'p' directive to either 'quarantine' or 'reject'. In addition, if the 'pct' directive is present, it must be set to a value other than zero. (The default is 100, which means to apply policy to all emails.)

MTA Strict Transport Security

SMTP Mail Transfer Agent Strict Transport Security (MTA-STS) is a mechanism enabling mail service providers to declare their ability to receive Transport Layer Security (TLS) secure SMTP connections, and to specify whether sending SMTP servers should refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.

Feature not implemented or disabled
Your server doesn't support this feature.

SMTP TLS Reporting

SMTP TLS Reporting (RFC 8460), or TLS-RPT for short, describes a reporting mechanism and format by which systems sending email can share statistics and specific information about potential failures with recipient domains. Recipient domains can then use this information to both detect potential attacks and diagnose unintentional misconfigurations. TLS-RPT can be used with DANE or MTA-STS.

Feature not implemented or disabled
Your server doesn't support this feature.

HTTP (80)

To observe your HTTP implementation, we submit a request to the homepage of your site on port 80, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers.

Test passed
Everything seems to be well configured. Well done.

URL: http://yahoo.co.jp/

1
http://yahoo.co.jp/
HTTP/1.1 301 Redirect
2
https://www.yahoo.co.jp/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

URL: http://www.yahoo.co.jp/

1
http://www.yahoo.co.jp/
HTTP/1.1 301 Redirect
2
https://www.yahoo.co.jp:443/
HTTP/1.1 200 OK

Analysis

Good
HTTP redirects to HTTPS
Good. This plaintext HTTP server redirects to HTTPS.

HTTP (443)

To observe your HTTPS implementation, we submit a request to the homepage of your site on port 443, follow all redirections (even when they take us to other domain names), and record the returned HTTP headers. We use the most recent set of headers returned from the tested hostname for further tests such as HSTS and HPKP.

Test passed
Everything seems to be well configured. Well done.

URL: https://yahoo.co.jp/

1
https://yahoo.co.jp/
HTTP/1.1 301 Redirect
2
https://www.yahoo.co.jp/
HTTP/1.1 200 OK

URL: https://www.yahoo.co.jp/

1
https://www.yahoo.co.jp/
HTTP/1.1 200 OK

WWW TLS

Transport Layer Security (TLS) is the most widely used encryption protocol on the Internet. In combination with valid certificates, servers can establish trusted communication channels even with users who have never visited them before. Network attackers can't uncover what is being communicated, even when they can see all the traffic.

Test passed
Everything seems to be well configured. Well done.

TLS Configuration: www.yahoo.co.jp (182.22.28.252)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yahoo.co.jp (182.22.59.229)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

TLS Configuration: yahoo.co.jp (183.79.135.206)

Encryption protocol version determines what features are
available for negotiation between client and server.
Supported protocols
TLS v1.3
TLS v1.2
Servers should always enforce their own cipher
suite preference, as that is the only approach
that guarantees that the best possible suite is
selected.
Server suite preference
Shows cipher suite configuration for this protocol version.TLS v1.3
Server preference
Suite: TLS_AES_256_GCM_SHA384
Suite ID: 0x1302
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_CHACHA20_POLY1305_SHA256
Suite ID: 0x1303
Cipher name: CHACHA20
Cipher strength: 256 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_CHACHA20_POLY1305_SHA256
 256 bits (ECDHE 256 bits)
Suite: TLS_AES_128_GCM_SHA256
Suite ID: 0x1301
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ecdh_x25519
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Shows cipher suite configuration for this protocol version.TLS v1.2
Server preference
Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0xc02f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0xc030
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0xc027
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Suite ID: 0xc028
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
 256 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0xc013
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
 128 bits (ECDHE 256 bits)
Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0xc014
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: ECDHE_RSA
Key exchange strength: EC ecdh_x25519 (256 bits)
Forward secrecy: Yes
PRF: SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
 256 bits (ECDHE 256 bits)
Suite: TLS_RSA_WITH_AES_128_GCM_SHA256
Suite ID: 0x9c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_GCM_SHA384
Suite ID: 0x9d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: AEAD
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA256
Suite ID: 0x3c
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Suite ID: 0x3d
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
 256 bits
Suite: TLS_RSA_WITH_AES_128_CBC_SHA
Suite ID: 0x2f
Cipher name: AES
Cipher strength: 128 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_128_CBC_SHA
 128 bits
Suite: TLS_RSA_WITH_AES_256_CBC_SHA
Suite ID: 0x35
Cipher name: AES
Cipher strength: 256 bits
Cipher block size: 128 bits
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_AES_256_CBC_SHA
 256 bits
Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA
Suite ID: 0xa
Cipher name: 3DES (WEAK)
Cipher strength: 112 bits
Cipher block size: 64 bits (WEAK)
Cipher mode: CBC
Key exchange: RSA
Key exchange strength: 2048 bits
Forward secrecy: No (WEAK)
PRF: SHA
TLS_RSA_WITH_3DES_EDE_CBC_SHA
 112 bits

Analysis

Good
TLS 1.3 supported
Excellent. This server supports TLS 1.3, which is the latest revision of the TLS protocol and a significant improvement over earlier versions. Developed over a period of several years and extensively analyzed prior to the release, TLS 1.3 removed insecure features, and improved both security and performance.
Good
TLS 1.2 supported
Good. This server supports TLS 1.2, which can provide strong security when configured correctly. This version of the TLS protocol is necessary to provide good security with a wide range of clients that don't yet support TLS 1.3.
Good
Deprecated protocols not supported
Excellent. This server doesn't support any of the deprecated protocol (TLS 1.1 and earlier).
Good
Strong key exchange detected
Excellent. All cipher suites on this server rely on strong key exchange. The sweet spot is 2048 bits for DHE and 256 bits for ECDHE. Putting ECDHE suites first guarantees best security and best performance.
Good
Server prefers forward secrecy and authenticated encryption suites
Excellent. Not only does this server enforce its server preference, but it also has at the top of the list suites that support both forward secrecy and authenticated encryption. This is the best TLS 1.2 can offer.
Good
Server enforces cipher suite preferences
Excellent. This server enforces server cipher suite preference, which means that it is able to select the best suite from the options submitted by clients. Combined with a well designed list of supported cipher suites, this settings enables negotiation of best security.
Good
All TLS connections with this server satisfy Apple's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Good
All TLS connections with this server satisfy Chrome's CT requirements
All TLS connections established with this server satisfy Chrome's CT requirements, using certificate, TLS extension, or OCSP response as SCT transport method.

SCT transports: CERT

Notice
DHE suites not supported
This server doesn't support the Diffie-Hellman (DH) key exchange.

WWW Certificates

A certificate is a digital document that contains a public key, some information about the entity associated with it, and a digital signature from the certificate issuer. It’s a mechanism that enables us to exchange, store, and use public keys. Being able to reliably verify the identity of a remote server is crucial in order to achieve secure encrypted communication.

Test passed
Everything seems to be well configured. Well done.

Certificate: yahoo.co.jp

Leaf certificate edge01.yahoo.co.jp
Issuer: Cybertrust Japan Co., Ltd.
Not Before: 23 Apr 2021 09:01:03 UTC
Not After: 22 May 2022 14:59:00 UTC (expires in 11 months 2 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.
Good
Certificate satisfies Chrome's CT compliance requirements
Good. This certificate satisfies Chrome's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
edge01.yahoo.co.jp | 801bc0e
Not After: 22 May 2022 14:59:00 UTC (expires in 11 months 2 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Cybertrust Japan SureServer CA G4 | 0207056
Not After: 29 May 2029 05:00:39 UTC (expires in 7 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
SECOM Trust Systems CO.,LTD. | c415ceb
Not After: 29 Sep 2023 02:22:35 UTC (expires in 2 years 3 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
SECOM Trust.net | e75e72e
Not After: 30 Sep 2023 04:20:49 UTC (expires in 2 years 3 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

Certificate: www.yahoo.co.jp

Leaf certificate edge01.yahoo.co.jp
Issuer: Cybertrust Japan Co., Ltd.
Not Before: 24 May 2021 01:00:59 UTC
Not After: 23 Jun 2022 14:59:00 UTC (expires in 1 year 3 days)
Key: RSA 2048 bits
Signature: SHA256withRSA
 View details

Analysis

Good
Strong private key
Good. The private key associated with this certificate is secure.
Good
Strong signature algorithm
Good. This certificate uses a strong signature algorithm.
Good
Certificate matches hostname
Good. The provided certificate matches the expected hostnames.
Good
Certificate dates match
Good. The certificate is valid for use at this point of time.
Good
Certificate has not been revoked
Good. This certificate has not been revoked.
Good
Certificate satisfies Apple's CT compliance requirements
Good. This certificate satisfies Apple's CT requirements at present.
Good
Certificate satisfies Chrome's CT compliance requirements
Good. This certificate satisfies Chrome's CT requirements at present.

Certificate Trust

Determining whether a certificate is considered valid is a complicated process that depends on the exact configuration of the validating party. For trust to be established, the certificate must form a chain that ends with a trusted root. In this section we evaluate the server's certificate against major root stores.

Platform Trusted
Apple
Google AOSP
Microsoft
Mozilla

Certificate Chain

For a server certificate to be valid, it must be presented as part of a complete and valid certificate chain. The last certificate in the chain should be the root and is usually not included in the configuration.

Leaf certificate
edge01.yahoo.co.jp | a0f9452
Not After: 23 Jun 2022 14:59:00 UTC (expires in 1 year 3 days)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
Cybertrust Japan SureServer CA G4 | 0207056
Not After: 29 May 2029 05:00:39 UTC (expires in 7 years 11 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Intermediate certificate
SECOM Trust Systems CO.,LTD. | c415ceb
Not After: 29 Sep 2023 02:22:35 UTC (expires in 2 years 3 months)
Authentication: RSA 2048 bits (SHA256withRSA)
 View details
Root certificate
SECOM Trust.net | e75e72e
Not After: 30 Sep 2023 04:20:49 UTC (expires in 2 years 3 months)
Authentication: RSA 2048 bits (SHA1withRSA)
 View details

Analysis

Good
Certificate chain is correct
Good. This chain contains all the right certificates and in the right order.

DANE (443)

DNS-based Authentication of Named Entities (DANE) is a bridge between DNSSEC and TLS. In one possible scenario, DANE can be used for public key pinning, building on an existing publicly-trusted certificate. In another approach, it can be used to completely bypass the CA ecosystem and establish trust using DNSSEC alone.

Feature not implemented or disabled
Your server doesn't support this feature.

Cookies

Cookies are small chunks of text that are sent between your browser and a website. They are often essential to the operation of the site and sometimes contain sensitive information. Session cookies sent from secure sites must be explicitly marked as secure to prevent being obtained by active network attackers.

Test passed, but there are warnings
Some aspect of your site's configuration require your attention.

HTTP Cookie: B

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
3ob0pl1gcte8b&b=3&s=n7
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
yahoo.co.jp
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.
Expires
Wed Jun 21 03:42:03 UTC 2023 (2 years 23 hours)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Warning
Cookie is not secure
This cookie, which has been sent over an encrypted channel, doesn't have the secure flag set. As a result, an active network attacker can easily recover it.

HTTP Cookie: XB

Cookie value. As far as the cookie RFC is concerned, the value
is an opaque string which only the application should interpret.
Value
3ob0pl1gcte8b&b=3&s=n7
Cookie domain. When domain is implied (not explicitly set in a cookie),
most browsers (but not IE) treat the cookie as host-only, meaning that
no other server can overwrite it.
Domain
yahoo.co.jp
Cookie path. This field can't be used as security measure,
but it could be of use to avoid cookie name collision
in non-adversarial contexts.
Path
/
Cookies are designed to always expire. Session cookies
are truly ephemeral and remain cached until the browser
is closed. The Expires and Max-Age cookie attributes can
be used to specify that a cookie should stay alive for
longer.
Expires
Wed Jun 21 03:42:03 UTC 2023 (2 years 23 hours)
The HttpOnly flag prevents the cookie from being accessed
from JavaScript, thus making them more difficult
to obtain after a successful XSS attack.
HttpOnly
The Secure flag signals to browsers that the cookie
should be transmitted only over an encrypted channel.
Secure
Normally, when a browser makes a request to a web site,
it sends all associated cookies. This is not always
desirable, because it might allow third-party sites
to perform site actions under the identity of the user.
This attack is known as Cross-Site Request Forgery.
With SameSite cookies (still in development, but already
supported in some browsers), you can choose to be more
strict. The possible values are 'lax' and 'strict'.
SameSite

Analysis

Good
Cookie is secure
Good. This cookie is marked secure, which means that it won't ever be transmitted over plaintext. As such, it's not vulnerable to the Sidejacking attack.

Mixed Content

On virtually all web sites, HTML markup, images, style sheets, JavaScript, and other page resources arrive not only over multiple connections but possibly from multiple servers and sites spread across the entire Internet. For a page to be properly encrypted, it’s necessary that all the content is retrieved over HTTPS. In practice, that’s very often not the case, leading to mixed content security problems.

Test passed
Everything seems to be well configured. Well done.

Embedded Resources

In this section we look at the security of all embedded resources. Mixed active content occurs when there are unprotected scripts or styles embedded in a page. This is typically not allowed by modern browsers. Mixed passive content (images, videos and such) are typically allowed, but shouldn't be present.

5 script(s)
  5 out of 5 are secure  View all
1 CSS file(s)
  1 out of 1 are secure  View all
4 media file(s)
  4 out of 4 are secure  View all

Outbound Links

Ideally, an encrypted page should only have links that lead to other encrypted pages. If plaintext links are used, passive network attackers can see where people go after they visit your web site. It's also possible that some sensitive information is leaked in the Referer header.

95 link(s)
  95 out of 95 are encrypted  View all

HTTP Strict Transport Security

HTTP Strict Transport Security (HSTS) vastly improves security of the network encryption layer. With HSTS enabled, browsers no longer allow clicking through certificate warnings errors, which are typically trivial to exploit. Additionally, they will no longer submit insecure (plaintext) requests to the site in question, even if asked.

Feature not implemented or disabled
Your server doesn't support this feature.

HSTS Policy

URL from which this policy was obtained.Location https://www.yahoo.co.jp/

Analysis

Powerup!
No parent protection
This host could benefit from further protection if the apex hostname would be configured with a HSTS policy that uses 'includeSubDomains'. Enabling HSTS on an entire domain name is the only approach that provides robust security.

Analysis

Powerup!
Deploy HSTS on this host
This host doesn't use HSTS, which means that its users can be easily attacked via MITM attacks. Consider deploying HSTS to disable certificate warnings and increase content and cookie security.
Powerup!
No HSTS on apex hostname
Even though the main host uses HSTS, the protection is not as good as it could be because the apex hostname doesn't have HSTS deployed. Without robust HSTS, attackers can sometimes abuse cookies and make up plaintext subdomains to use for phishing.

Location: https://yahoo.co.jp

HTTP Public Key Pinning

HTTP Public Key Pinning (HPKP) enables site operators to restrict which certificates are considered valid for their domain names. With a valid HPKP configuration, sites can defeat man in the middle (MITM) attacks using fraudulent or misissued certificates. HPKP is an advanced feature, suitable for use by only high-profile web sites.

Feature not implemented or disabled
Your server doesn't support this feature.

Content Security Policy

Content Security Policy (CSP) is a security mechanism that allows web sites control how browsers process their pages. In essence, sites can restrict what types of resources are loaded and from where. CSP policies can be used to defend against cross-site scripting, prevent mixed content issues, as well as report violations for investigation.

Feature not implemented or disabled
Your server doesn't support this feature.

Subresource Integrity

Subresource Integrity (SRI) is a new standard that enables browsers to verify the integrity of embedded page resources (e.g., scripts and stylesheets) when they are loaded from third-party web sites. With SRI deployed, remote resources can be used safely, without fear of them being modified by malicious parties.

Feature not implemented or disabled
Your server doesn't support this feature.
5 script(s)
  0 out of 5 are secure
https://s.yimg.jp/...7/bundle_20210617.js
https://yads.c.yimg.jp/js/yads-async.js
https://yads.c.yimg.jp/uadf/yads_vimps.js
https://s.yimg.jp/...mmon/js/iicon.min.js
https://yads.c.yimg.jp/js/yads-async.js
 View all
1 CSS file(s)
  0 out of 1 are secure
https://s.yimg.jp/.../bundle_20210617.css
 View all

Analysis

Powerup!
SRI required
This page contains remote resources that are under the control of third parties. Deploy SRI to protect them from modification.

Expect CT

Expect-CT is a response HTTP header that web sites can use to monitor problems related to their Certificate Transparency (CT) compliance. Should any CT issues arise, browsers that support this header will submit reports to the specified reporting endpoint.

Feature not implemented or disabled
Your server doesn't support this feature.

Analysis

Powerup!
Deploy Expect-CT to enable reporting
An Expect-CT policy enables web sites to monitor for any problems related to their Expect-CT compliance, detecting potentially serious issues quickly. When issues arise, compliant browsers will submit reports to the specified reporting endpoints. Before CT become required for all public certificates the Expect-CT was also used to require CT, but that use case no longer applies.

Frame Options

The X-Frame-Options header controls page framing, which occurs when a page is incorporated into some other page, possibly on a different site. If framing is allowed, attackers can employ clever tricks to make victims perform arbitrary actions on your site; they do this by showing their web site while forwarding the victim's clicks to yours.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Frame-Options

Value: SAMEORIGIN

Good
Framing allowed from the same origin only
OK. Your site allows page framing only from itself. This should generally be safe, except maybe on sites that host user content.

XSS Protection

Modern browsers ship with built-in defenses against Cross-Site Scripting (XSS), usually known as XSS Auditors. Web sites are allowed to control the defenses if they specify an X-XSS-Protection header in their HTTP responses. Recommended policies are either to block XSS attacks, or disable the defenses if you think false positives are possible. Filtering, where offending fragments of data are removed, is not recommended because it can be abused by attackers to selectively deactivate script files.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Xss-Protection

Value: 1; mode=block

Good
Valid configuration
Good. Your configuration enforces blocking when XSS attacks are detected.

Content Type Options

Some browsers use a technique called content sniffing to override response MIME types provided by HTTP servers and interpret responses as something else (usually HTML). This behavior, which could potentially lead to security issues, should be disabled by attaching an X-Content-Type-Options header to all responses.

Test passed
Everything seems to be well configured. Well done.

Analysis

Info
Header information

Name: X-Content-Type-Options

Value: nosniff

Good
Valid configuration
Good. Your configuration is valid. This means that browsers won't try to guess file MIME type on this web site.

HTML Analysis

Analysis of page content, including SRI.

Test passed
Everything seems to be well configured. Well done.

Base URL

https://www.yahoo.co.jp/

Active Content

Type Status Location
script Third-party [invalid]
script Third-party yads.c.yimg.jp
script Third-party yads.c.yimg.jp
script Third-party s.yimg.jp
script Third-party yads.c.yimg.jp
css Third-party [invalid]

Passive Content

Type Status Link
media Third-party b.yjtag.jp
media Third-party news-pctr.c.yimg.jp
media Third-party s.yimg.jp
media Third-party s.yimg.jp

Links

Type Status Link
link Encrypted rdsig.yahoo.co.jp
link Encrypted kids.yahoo.co.jp
link Encrypted promo-mobile.yahoo.co.jp
link Encrypted support.yahoo-net.jp
link Encrypted ext.yahoo.co.jp
link Encrypted paypaystep.yahoo.co.jp
link Encrypted card.yahoo.co.jp
link Encrypted mail.yahoo.co.jp
link Encrypted travel.yahoo.co.jp
link Encrypted auctions.yahoo.co.jp
link Encrypted shopping.yahoo.co.jp
link Encrypted search.yahoo.co.jp
link Encrypted search.yahoo.co.jp
link Encrypted search.yahoo.co.jp
link Encrypted chiebukuro.yahoo.co.jp
link Encrypted map.yahoo.co.jp
link Encrypted search.yahoo.co.jp
link Encrypted services.yahoo.co.jp
link Encrypted support.yahoo-net.jp
link Encrypted shopping.geocities.jp
link Encrypted yellmarket.yahoo.co.jp
link Encrypted smartphone.yahoo.co.jp
link Encrypted shopping.yahoo.co.jp
link Encrypted paypaymall.yahoo.co.jp
link Encrypted auctions.yahoo.co.jp
link Encrypted app.adjust.com
link Encrypted zozo.jp
link Encrypted lohaco.jp
link Encrypted travel.yahoo.co.jp
link Encrypted www.ikyu.com
link Encrypted restaurant.ikyu.com
link Encrypted demae-can.com
link Encrypted news.yahoo.co.jp
link Encrypted weather.yahoo.co.jp
link Encrypted sports.yahoo.co.jp
link Encrypted finance.yahoo.co.jp
link Encrypted tv.yahoo.co.jp
link Encrypted movies.yahoo.co.jp
link Encrypted gyao.yahoo.co.jp
link Encrypted music.line.me
link Encrypted games.yahoo.co.jp
link Encrypted ebookjapan.yahoo.co.jp
link Encrypted fortune.yahoo.co.jp
link Encrypted map.yahoo.co.jp
link Encrypted transit.yahoo.co.jp
link Encrypted retty.me
link Encrypted www.kurashiru.com
link Encrypted jp.stanby.com
link Encrypted realestate.yahoo.co.jp
link Encrypted carview.yahoo.co.jp
link Encrypted trilltrill.jp
link Encrypted my-best.com
link Encrypted services.yahoo.co.jp
link Encrypted business.yahoo.co.jp
link Encrypted www.paypay-corp.co.jp
link Encrypted ads-promo.yahoo.co.jp
link Encrypted business-ec.yahoo.co.jp
link Encrypted dataforest.yahoo.co.jp
link Encrypted bank.yahoo.co.jp
link Encrypted about.yahoo.co.jp
link Encrypted donation.yahoo.co.jp
link Encrypted volunteer.yahoo.co.jp
link Encrypted yellmarket.yahoo.co.jp
link Encrypted kikin.yahoo.co.jp
link Encrypted about.yahoo.co.jp
link Encrypted team.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted news.yahoo.co.jp
link Encrypted login.yahoo.co.jp
link Encrypted account.edit.yahoo.co.jp
link Encrypted login.yahoo.co.jp
link Encrypted mail.yahoo.co.jp
link Encrypted points.yahoo.co.jp
link Encrypted wallet.yahoo.co.jp
link Encrypted login.yahoo.co.jp
link Encrypted login.yahoo.co.jp