Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout, 5 invalid Headers

Checked:
03.04.2024 04:39:42

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
vl-tokyo.co.jp	A	182.16.226.147 Toyama/Japan (JP) - A.T.WORKS, Inc. Hostname: onx06.atw.ne.jp	yes	1	0
	AAAA		yes
www.vl-tokyo.co.jp	CNAME	d32313h9zyja9j.cloudfront.net	yes	1	0
	A	3.162.79.15 Berlin/Land Berlin/Germany (DE) - Amazon.com, Inc. Hostname: server-3-162-79-15.txl50.r.cloudfront.net	yes
	A	3.162.79.37 Berlin/Land Berlin/Germany (DE) - Amazon.com, Inc. Hostname: server-3-162-79-37.txl50.r.cloudfront.net	yes
	A	3.162.79.40 Berlin/Land Berlin/Germany (DE) - Amazon.com, Inc. Hostname: server-3-162-79-40.txl50.r.cloudfront.net	yes
	A	3.162.79.123 Berlin/Land Berlin/Germany (DE) - Amazon.com, Inc. Hostname: server-3-162-79-123.txl50.r.cloudfront.net	yes
*.vl-tokyo.co.jp	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 5613, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 30903, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2024, 00:00:00 +, Signature-Inception: 01.04.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: jp
jp	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 22111, DigestType 2 and Digest 5aQ1NLm+r7811saz6qHprn/itNiWElISb9Z7UXIyIoY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner jp., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2024, 18:00:00 +, Signature-Inception: 02.04.2024, 17:00:00 +, KeyTag 5613, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 5613 used to validate the DS RRSet in the parent zone


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 14481, Flags 256


	Public Key with Algorithm 8, KeyTag 22111, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 25581, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner jp., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.05.2024, 18:45:00 +, Signature-Inception: 08.03.2024, 18:45:00 +, KeyTag 22111, Signer-Name: jp


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22111 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 22111, DigestType 2 and Digest "5aQ1NLm+r7811saz6qHprn/itNiWElISb9Z7UXIyIoY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: co.jp
co.jp	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "k8d2hbb9bvgeh428nrio4qriub51ndg0" between the hashed NSEC3-owner "k8d2hbb9bvgeh428nrio4qriub51ndg0" and the hashed NextOwner "k8dj2s43ibdj8qspiahojjssiaqqkbft". So the parent zone confirmes the not-existence of a DS RR. Bitmap: TXT, RRSIG Validated: RRSIG-Owner k8d2hbb9bvgeh428nrio4qriub51ndg0.jp., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 29.04.2024, 17:45:02 +, Signature-Inception: 30.03.2024, 17:45:02 +, KeyTag 14481, Signer-Name: jp


	0 DNSKEY RR found




Zone: vl-tokyo.co.jp
vl-tokyo.co.jp	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "h47q702ht5idvj3qv4bmpgd5ke27qcu6" between the hashed NSEC3-owner "h46aj0jb5sutp1051c5m5r898guhe3jk" and the hashed NextOwner "h48ppbgpcvuvpmb2o4kn5eo4pm9oqibt". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner h46aj0jb5sutp1051c5m5r898guhe3jk.jp., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 29.04.2024, 17:45:02 +, Signature-Inception: 30.03.2024, 17:45:02 +, KeyTag 14481, Signer-Name: jp


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k8d2hbb9bvgeh428nrio4qriub51ndg0" as Owner. That's the Hash of "co.jp" with the NextHashedOwnerName "k8dj2s43ibdj8qspiahojjssiaqqkbft". So that domain name is the Closest Encloser of "vl-tokyo.co.jp". Opt-Out: True. Bitmap: TXT, RRSIG Validated: RRSIG-Owner k8d2hbb9bvgeh428nrio4qriub51ndg0.jp., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 29.04.2024, 17:45:02 +, Signature-Inception: 30.03.2024, 17:45:02 +, KeyTag 14481, Signer-Name: jp


	0 DNSKEY RR found




Zone: www.vl-tokyo.co.jp
www.vl-tokyo.co.jp	0 DS RR in the parent zone found

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 5613, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 30903, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2024, 00:00:00 +, Signature-Inception: 01.04.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: net
net	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2024, 18:00:00 +, Signature-Inception: 02.04.2024, 17:00:00 +, KeyTag 5613, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 5613 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 34730, Flags 256


	Public Key with Algorithm 13, KeyTag 37331, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.04.2024, 14:10:35 +, Signature-Inception: 28.03.2024, 14:05:35 +, KeyTag 37331, Signer-Name: net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 37331 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: cloudfront.net
cloudfront.net	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "fadg3thgago5pl3lsi24ljmgetcjvkk8" between the hashed NSEC3-owner "fadetbe5n02d22kctsbu3tm86mf8eacj" and the hashed NextOwner "fadg4mls25nqik90m8ep414g1d463o55". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fadetbe5n02d22kctsbu3tm86mf8eacj.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 09.04.2024, 06:57:00 +, Signature-Inception: 02.04.2024, 05:47:00 +, KeyTag 34730, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "cloudfront.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.04.2024, 06:52:58 +, Signature-Inception: 30.03.2024, 05:42:58 +, KeyTag 34730, Signer-Name: net


	0 DNSKEY RR found




Zone: d32313h9zyja9j.cloudfront.net
d32313h9zyja9j.cloudfront.net	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
vl-tokyo.co.jp	• ns.dlsv.com	210.236.247.71 Chiyoda/Tokyo/Japan (JP) - IDC Frontier Inc.	•
	• ns0.atw.jp	182.16.226.200 Toyama/Japan (JP) - A.T.WORKS, Inc.	•
	• ns1.atw.jp	210.236.247.71 Chiyoda/Tokyo/Japan (JP) - IDC Frontier Inc.	•
	• ns2.atw.jp	219.99.220.242 Tachibana/Ishikawa/Japan (JP) - NSK Co., Ltd.	•
	• ns2.dlsv.com	219.99.220.242 Tachibana/Ishikawa/Japan (JP) - NSK Co., Ltd.	•
	• ns3.atw.jp	182.16.226.193 Toyama/Japan (JP) - A.T.WORKS, Inc.	•
	• ns3.dlsv.com	182.16.226.193 Toyama/Japan (JP) - A.T.WORKS, Inc.	•
co.jp	• z.dns.jp / a21.osa	203.119.1.10 Chiyoda/Tokyo/Japan (JP) - Japan Registry Service Co., Ltd.	•
jp	• a.dns.jp / a22.osa		•
	• b.dns.jp / ns0h.dixie		•
	• c.dns.jp / TLD_Host2.Frankfurt_Node1		•
	• d.dns.jp / d162.d.dns.jp		•
	• e.dns.jp / cdg1.edns.jp		•
	• f.dns.jp / f-dnssec2		•
	• g.dns.jp / g21.tyo		•
	• h.dns.jp / app19.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• z.dns.jp

d32313h9zyja9j.cloudfront.net	• ns-1396.awsdns-46.org / e9fac45c500939371cbcfffbdc249869 -	205.251.197.116 Dublin/Leinster/Ireland (IE) - Amazon.com	•
	•	2600:9000:5305:7400::1 London/England/United Kingdom (GB) - Amazon.com	•
	• ns-1710.awsdns-21.co.uk / e3fc9b2808eabb1791c00963e5c52f3d -	205.251.198.174 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:ae00::1 Seattle/Washington/United States (US) - Amazon.com	•
	• ns-424.awsdns-53.com / b085e4b5e9f11bafe4c40a599f175633 -	205.251.193.168 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5301:a800::1 Seattle/Washington/United States (US) - Amazon.com	•
	• ns-953.awsdns-55.net / eb12218d62588fcb4a090396a7bcc6fc -	205.251.195.185 Sterling/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5303:b900::1 Seattle/Washington/United States (US) - Amazon.com	•
cloudfront.net	• ns-1306.awsdns-35.org / 40bd453279d22c134f4815b90ed782f4 -	205.251.197.26 Dublin/Leinster/Ireland (IE) - Amazon.com	•
	•	2600:9000:5305:1a00::1 London/England/United Kingdom (GB) - Amazon.com	•
	• ns-1597.awsdns-07.co.uk / 98812c59dd8862a8e1c0d19360e7a4fd -	205.251.198.61 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:3d00::1 Seattle/Washington/United States (US) - Amazon.com	•
	• ns-418.awsdns-52.com / 3d0d1fc7053a960a860a00dd179e6c72 -	205.251.193.162 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5301:a200::1 Seattle/Washington/United States (US) - Amazon.com	•
	• ns-666.awsdns-19.net / eb12218d62588fcb4a090396a7bcc6fc -	205.251.194.154 Sterling/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5302:9a00::1 Seattle/Washington/United States (US) - Amazon.com	•
net	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-defra-5		•
	• d.gtld-servers.net / nnn1-defra-5		•
	• e.gtld-servers.net / nnn1-defra-5		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-ein4		•
	• k.gtld-servers.net / nnn1-ein2		•
	• l.gtld-servers.net / nnn1-nlams-2e		•
	• m.gtld-servers.net / nnn1-ein3		•

4. SOA-Entries

Domain:	jp
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	jp
Zone-Name:	jp
Primary:	z.dns.jp
Mail:	root.dns.jp
Serial:	1712111402
Refresh:	3600
Retry:	900
Expire:	1814400
TTL:	900
num Entries:	8

Domain:	co.jp
Zone-Name:	jp
Primary:	z.dns.jp
Mail:	root.dns.jp
Serial:	1712111402
Refresh:	3600
Retry:	900
Expire:	1814400
TTL:	900
num Entries:	1

Domain:	vl-tokyo.co.jp
Zone-Name:	vl-tokyo.co.jp
Primary:	ns0.atw.jp
Mail:	hostmaster.atw.jp
Serial:	2024030401
Refresh:	10800
Retry:	1800
Expire:	3600000
TTL:	600
num Entries:	7


Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112093
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	1

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112093
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	1

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112103
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	11

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112103
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	11

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112118
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	1

Domain:	net
Zone-Name:	net
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1712112118
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	1

Domain:	cloudfront.net
Zone-Name:	cloudfront.net
Primary:	ns-418.awsdns-52.com
Mail:	hostmaster.cloudfront.net
Serial:	1377556270
Refresh:	16384
Retry:	2048
Expire:	1048576
TTL:	60
num Entries:	8

Domain:	d32313h9zyja9j.cloudfront.net
Zone-Name:	d32313h9zyja9j.cloudfront.net
Primary:	ns-1710.awsdns-21.co.uk
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	8

5. Screenshots

Startaddress: https://www.vl-tokyo.co.jp/, address used: https://www.vl-tokyo.co.jp/, Screenshot created 2024-04-03 04:45:29 +00:0

Mobil (412px x 732px)

1096 milliseconds

Screenshot mobile - https://www.vl-tokyo.co.jp/

Mobil + Landscape (732px x 412px)

1094 milliseconds

Screenshot mobile landscape - https://www.vl-tokyo.co.jp/

Screen (1280px x 1680px)

2038 milliseconds

Screenshot Desktop - https://www.vl-tokyo.co.jp/

Mobile- and other Chrome-Checks

	width	height
visual Viewport	396	732
content Size	396	3145

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://vl-tokyo.co.jp/ 182.16.226.147	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.46 %	0.566	E
Server: nginx
Date: Wed, 03 Apr 2024 02:43:26 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
Content-Type: text/html
Content-Length: 162

• http://www.vl-tokyo.co.jp/ 3.162.79.15	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.15 %	0.010	A
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:27 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
X-Cache: Redirect from cloudfront
Via: 1.1 e1997deca771cb54e2886aed779bc92c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: WRQlDqZl2fDasKf15O9cq2wZzNMZkYpfShaaVa4KeC90NFYeSkFFnQ==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/ 3.162.79.37	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.15 %	0.010	A
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:27 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
X-Cache: Redirect from cloudfront
Via: 1.1 7a65f4d2ee5d57076ba751b6931848de.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: UbxlK3fkIGcO9mg1H3Kd_gqmiY4z6cOvXyP_y-Rbu6tEORGC2PrS8A==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/ 3.162.79.40	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.15 %	0.010	A
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:27 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
X-Cache: Redirect from cloudfront
Via: 1.1 ebe5c7b82bb332f597b412a5fb9a8910.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: puI5IGGZOoHoMXM6LfUUPErxg7-l_PZnB5oF7YppM60XpVsS4qfmfA==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/ 3.162.79.123	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.15 %	0.013	A
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:27 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
X-Cache: Redirect from cloudfront
Via: 1.1 7c0e584d1165bf617544d868dc892940.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: yDks1_uyP8SuD3-f6pfzJIaKr3zXJ8z8YNzaif85jcntPhvdLIuBtw==
Content-Type: text/html
Content-Length: 167

• https://vl-tokyo.co.jp/ 182.16.226.147	301	https://www.vl-tokyo.co.jp/ Html is minified: 109.46 %	10.016	B
Server: nginx
Date: Wed, 03 Apr 2024 02:43:28 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/
Content-Type: text/html
Content-Length: 162

• https://www.vl-tokyo.co.jp/ 3.162.79.15 No Compression used - 4347 / 11651 - 37.31 % possible Inline-JavaScript (∑/total): 6/1364 Inline-CSS (∑/total): 0/0	200	Html is minified: 157.04 % Other inline scripts (∑/total): 2/1364	3.916	I-
Transfer-Encoding: chunked
Connection: close
Date: Wed, 03 Apr 2024 02:43:43 GMT
Server: Apache
Strict-Transport-Security: max-age=315360000;
X-Cache: Miss from cloudfront
Via: 1.1 ecac8e61be1e296c21a67e56243778f8.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: z585IdaPdaHbg6HnwCGycPMr1CkxhZzXE91wmElCg8SNW1RMmai2YA==
Content-Type: text/html; charset=UTF-8
Last-Modified: Tue, 26 Mar 2024 04:34:12 GMT

• https://www.vl-tokyo.co.jp/ 3.162.79.37 No Compression used - 4347 / 11651 - 37.31 % possible Inline-JavaScript (∑/total): 6/1364 Inline-CSS (∑/total): 0/0	200	Html is minified: 157.04 % Other inline scripts (∑/total): 2/1364	2.736	I-
Transfer-Encoding: chunked
Connection: close
Server: Apache
Strict-Transport-Security: max-age=315360000;
Date: Wed, 03 Apr 2024 02:43:48 GMT
Vary: Accept-Encoding
X-Cache: RefreshHit from cloudfront
Via: 1.1 a9720b560aaea240abc824a2208068a2.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: -qfevcudvrH1_hgnbYr153XqZaPl7-dyT3muEJ5iRbuHSKil1GupIQ==
Content-Type: text/html; charset=UTF-8
Last-Modified: Tue, 26 Mar 2024 04:34:12 GMT

• https://www.vl-tokyo.co.jp/ 3.162.79.40 No Compression used - 4347 / 11651 - 37.31 % possible Inline-JavaScript (∑/total): 6/1364 Inline-CSS (∑/total): 0/0	200	Html is minified: 157.04 % Other inline scripts (∑/total): 2/1364	3.103	I-
Transfer-Encoding: chunked
Connection: close
Server: Apache
Strict-Transport-Security: max-age=315360000;
Date: Wed, 03 Apr 2024 02:43:52 GMT
Vary: Accept-Encoding
X-Cache: RefreshHit from cloudfront
Via: 1.1 365a977b864574759e83e211b333db7e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: JLnqNBC1KnqZhiTk_kCacAn6RHvkPlQXLzsxIry2nSv9S_9U65DpwQ==
Content-Type: text/html; charset=UTF-8
Last-Modified: Tue, 26 Mar 2024 04:34:12 GMT

• https://www.vl-tokyo.co.jp/ 3.162.79.123 No Compression used - 4347 / 11651 - 37.31 % possible Inline-JavaScript (∑/total): 6/1364 Inline-CSS (∑/total): 0/0	200	Html is minified: 157.04 % Other inline scripts (∑/total): 2/1364	3.653	I-
Transfer-Encoding: chunked
Connection: close
Date: Wed, 03 Apr 2024 02:43:39 GMT
Server: Apache
Strict-Transport-Security: max-age=315360000;
X-Cache: Miss from cloudfront
Via: 1.1 a259e473ed71960eef79d73efea6bc7e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: UnLlamPv5Kr6GDsARymTnp7h06aWsDc7nRo_wiHv0wU12mgRIa5Zmg==
Content-Type: text/html; charset=UTF-8
Last-Modified: Tue, 26 Mar 2024 04:34:12 GMT

• http://vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 182.16.226.147 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.46 % Other inline scripts (∑/total): 0/0	0.560	E
Visible Content:
Server: nginx
Date: Wed, 03 Apr 2024 02:43:56 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 162

• http://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.162.79.15 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.15 % Other inline scripts (∑/total): 0/0	0.007	A
Visible Content:
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:56 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Cache: Redirect from cloudfront
Via: 1.1 8562aa55ecb1bd657c9073c0910ec6bc.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: 1fb3rx0JB_F3xXCfY8DcH3o-WVVUQN0J0D8Zy5yHlWPrwQsOQ_xibA==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.162.79.37 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.15 % Other inline scripts (∑/total): 0/0	0.007	A
Visible Content:
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:56 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Cache: Redirect from cloudfront
Via: 1.1 ecac8e61be1e296c21a67e56243778f8.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: 7pGMIOLUNS9uUTEjX6FT5XLiw4ZuiLOhjM9WgMzYMZcIoaXC-93Qcg==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.162.79.40 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.15 % Other inline scripts (∑/total): 0/0	0.010	A
Visible Content:
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:56 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Cache: Redirect from cloudfront
Via: 1.1 9ee238dabfd91568e86792245c9ebb28.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: oJybKrnPWK1MycU6stOtglE-HghleNQwClgBozNhlok25oXnK9SW6A==
Content-Type: text/html
Content-Length: 167

• http://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.162.79.123 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 109.15 % Other inline scripts (∑/total): 0/0	0.010	A
Visible Content:
Server: CloudFront
Date: Wed, 03 Apr 2024 02:43:56 GMT
Connection: close
Location: https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
X-Cache: Redirect from cloudfront
Via: 1.1 9e5ec6086358ec6bc142d90efec366a2.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: CWpp4AKb9E2xhXkpjQEVKqxx7aPnB69BMn4_T5fz5nDANBcOe6JJCA==
Content-Type: text/html
Content-Length: 167

• https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 110.61 % Other inline scripts (∑/total): 0/0	3.053	A-
Not Found
Visible Content:
Transfer-Encoding: chunked
Connection: close
Date: Wed, 03 Apr 2024 02:44:07 GMT
Server: nginx
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer-when-downgrade
Content-Security-Policy: default-src 'self' http: https: ws: wss: data: blob: 'unsafe-inline'; frame-ancestors 'self';
Permissions-Policy: interest-cohort=()
Strict-Transport-Security: max-age=315360000;
Vary: Accept-Encoding
X-Cache: Error from cloudfront
Via: 1.1 9e5ec6086358ec6bc142d90efec366a2.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P5
X-Amz-Cf-Id: zEvHWJeehIxOx1fMO0aS1E1I1xVKRzssZLKm9GpwK8z2ql4Z20aikA==
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip

• https://3.162.79.15/ 3.162.79.15	-16		0.010	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://3.162.79.37/ 3.162.79.37	-16		0.010	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://3.162.79.40/ 3.162.79.40	-16		0.007	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://3.162.79.123/ 3.162.79.123	-16		0.013	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://182.16.226.147/ 182.16.226.147 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	200	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	8.130	N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx
Date: Wed, 03 Apr 2024 02:43:57 GMT
Connection: close
ETag: "10-5a17db92ab793"
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 16
Last-Modified: Mon, 23 Mar 2020 04:03:53 GMT

7. Comments

	1. General Results, most used to calculate the result
A	name "vl-tokyo.co.jp" is domain, public suffix is ".co.jp", top-level-domain is ".jp", top-level-domain-type is "country-code", Country is Japan, tld-manager is "Japan Registry Services Co., Ltd.", num .jp-domains preloaded: 1209 (complete: 240622)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: www.vl-tokyo.co.jp has 4 different ip addresses (authoritative).
	Warning: Only one ip address found: vl-tokyo.co.jp has only one ip address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: vl-tokyo.co.jp has no ipv6 address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.vl-tokyo.co.jp has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: www is preferred
A	Good: No cookie sent via http.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):5 complete Content-Type - header (6 urls)
	https://182.16.226.147/ 182.16.226.147			Url with incomplete Content-Type - header - missing charset
A	http://www.vl-tokyo.co.jp/ 3.162.79.15	301	https://www.vl-tokyo.co.jp/	Correct redirect http - https with the same domain name
A	http://www.vl-tokyo.co.jp/ 3.162.79.37	301	https://www.vl-tokyo.co.jp/	Correct redirect http - https with the same domain name
A	http://www.vl-tokyo.co.jp/ 3.162.79.40	301	https://www.vl-tokyo.co.jp/	Correct redirect http - https with the same domain name
A	http://www.vl-tokyo.co.jp/ 3.162.79.123	301	https://www.vl-tokyo.co.jp/	Correct redirect http - https with the same domain name
B	https://vl-tokyo.co.jp/ 182.16.226.147	301		Missing HSTS-Header
B	https://www.vl-tokyo.co.jp/ 3.162.79.15	200	max-age=315360000;	Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
B	https://www.vl-tokyo.co.jp/ 3.162.79.37	200	max-age=315360000;	Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
B	https://www.vl-tokyo.co.jp/ 3.162.79.40	200	max-age=315360000;	Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
B	https://www.vl-tokyo.co.jp/ 3.162.79.123	200	max-age=315360000;	Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
B	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	max-age=315360000;	Critical: HSTS-Header has Parse-Errors. Empty entry, remove the semicolon at the end., Unknown directive found. Only max-age (with value), includeSubdomains or preload allowed.
E	http://vl-tokyo.co.jp/ 182.16.226.147	301	https://www.vl-tokyo.co.jp/	Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
I	https://www.vl-tokyo.co.jp/ 3.162.79.123	200		Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
I	https://www.vl-tokyo.co.jp/ 3.162.79.15	200		Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
I	https://www.vl-tokyo.co.jp/ 3.162.79.37	200		Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
I	https://www.vl-tokyo.co.jp/ 3.162.79.40	200		Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
N	https://182.16.226.147/ 182.16.226.147	200		Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.vl-tokyo.co.jp, 4 ip addresses.
	Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain vl-tokyo.co.jp, 1 ip addresses.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.vl-tokyo.co.jp, 4 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.vl-tokyo.co.jp
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
F	www.vl-tokyo.co.jp 3.162.79.15	Content-Security-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.15	X-Content-Type-Options		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.15	Referrer-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.15	Permissions-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.37	Content-Security-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.37	X-Content-Type-Options		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.37	Referrer-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.37	Permissions-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.40	Content-Security-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.40	X-Content-Type-Options		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.40	Referrer-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.40	Permissions-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.123	Content-Security-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.123	X-Content-Type-Options		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.123	Referrer-Policy		Critical: Missing Header:
F	www.vl-tokyo.co.jp 3.162.79.123	Permissions-Policy		Critical: Missing Header:
	3. DNS- and NameServer - Checks
A	Info:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 7 Name Servers.
A	Info:: 6 Queries complete, 4 with IPv6, 2 with IPv4.
	Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns.dlsv.com (210.236.247.71), ns1.atw.jp (210.236.247.71), ns2.atw.jp (219.99.220.242), ns2.dlsv.com (219.99.220.242), ns3.atw.jp (182.16.226.193), ns3.dlsv.com (182.16.226.193)
A	Good (1 - 3.0):: An average of 0.9 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 7 different Name Servers found: ns.dlsv.com, ns0.atw.jp, ns1.atw.jp, ns2.atw.jp, ns2.dlsv.com, ns3.atw.jp, ns3.dlsv.com, 3 Name Servers included in Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, 3 Name Servers included in 1 Zone definitions: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp, 1 Name Servers listed in SOA.Primary: ns0.atw.jp.
A	Good: Only one SOA.Primary Name Server found.: ns0.atw.jp.
	Error: SOA.Primary Name Server not included in the delegation set.: ns0.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns.dlsv.com (210.236.247.71): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns0.atw.jp (182.16.226.200): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.atw.jp (210.236.247.71): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.atw.jp (219.99.220.242): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.dlsv.com (219.99.220.242): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.atw.jp (182.16.226.193): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.dlsv.com (182.16.226.193): Delegation: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com, Zone: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp. Name Servers defined in Delegation, missing in Zone: ns.dlsv.com, ns2.dlsv.com, ns3.dlsv.com.Name Servers defined in Zone, missing in Delegation: ns1.atw.jp, ns2.atw.jp, ns3.atw.jp.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 7 different Name Servers found
	Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 7 different Name Servers found
A	Good: Name servers with different Top Level Domains / Public Suffix List entries found: 7 Name Servers, 2 Top Level Domains: jp, com
A	Good: Name Servers with different domain names found.: 2 different Domains found
	Warning: All Name Servers from the same Country / IP location.: 7 Name Servers, 1 Countries: JP
A	Info: Ipv4-Subnet-list: 7 Name Servers, 3 different subnets (first Byte): 182., 210., 219., 3 different subnets (first two Bytes): 182.16., 210.236., 219.99., 3 different subnets (first three Bytes): 182.16.226., 210.236.247., 219.99.220.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
A	Good: Nameserver supports TCP connections: 7 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 7 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 7 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 7 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: z.dns.jp: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: amazonaws.com is allowed to create wildcard-certificates
A	Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
	4. Content- and Performance-critical Checks
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	https://www.vl-tokyo.co.jp/ 3.162.79.15	200		Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
	https://www.vl-tokyo.co.jp/ 3.162.79.37	200		Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
	https://www.vl-tokyo.co.jp/ 3.162.79.40	200		Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
	https://www.vl-tokyo.co.jp/ 3.162.79.123	200		Warning: https result with status 200 and size greater then 1024 Bytes without Compression found. Add Compression support (gzip, deflate, br - these are checked) so the html content is compressed.
	https://www.vl-tokyo.co.jp/ 3.162.79.15	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://www.vl-tokyo.co.jp/ 3.162.79.37	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://www.vl-tokyo.co.jp/ 3.162.79.40	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://www.vl-tokyo.co.jp/ 3.162.79.123	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://www.vl-tokyo.co.jp/ 3.162.79.15	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
	https://www.vl-tokyo.co.jp/ 3.162.79.37	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
	https://www.vl-tokyo.co.jp/ 3.162.79.40	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
	https://www.vl-tokyo.co.jp/ 3.162.79.123	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
A	Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
	https://www.vl-tokyo.co.jp/ 3.162.79.15	200		Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 4 script elements without defer/async.
	https://www.vl-tokyo.co.jp/ 3.162.79.37	200		Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 4 script elements without defer/async.
	https://www.vl-tokyo.co.jp/ 3.162.79.40	200		Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 4 script elements without defer/async.
	https://www.vl-tokyo.co.jp/ 3.162.79.123	200		Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 4 script elements without defer/async.
A	Good: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 40 external CSS / JavaScript files found
A	Good: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 28 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed
	Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 32 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 8 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 40 complete.
	Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 36 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 36 complete.
A	Good: All checked attribute values are enclosed in quotation marks (" or ').
A	Good: Some img-elements have a valid alt-attribute.: 36 img-elements found, 28 img-elements with correct alt-attributes (defined, not an empty value).
	Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 8 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
	https://www.vl-tokyo.co.jp/ 3.162.79.15	200	Strict-Transport-Security: max-age=315360000;	Parse Error - Header can't be parsed
	https://www.vl-tokyo.co.jp/ 3.162.79.37	200	Strict-Transport-Security: max-age=315360000;	Parse Error - Header can't be parsed
	https://www.vl-tokyo.co.jp/ 3.162.79.40	200	Strict-Transport-Security: max-age=315360000;	Parse Error - Header can't be parsed
	https://www.vl-tokyo.co.jp/ 3.162.79.123	200	Strict-Transport-Security: max-age=315360000;	Parse Error - Header can't be parsed
	https://www.vl-tokyo.co.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	3.053 seconds	Warning: 404 needs more then one second
A	Info: Different Server-Headers found
A	Duration: 368670 milliseconds, 368.670 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

vl-tokyo.co.jp

182.16.226.147

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

vl-tokyo.co.jp

182.16.226.147

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

http/2 via ALPN supported
SNI required

Tls.1.2
no Tls.1.1
Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
SNI required

Tls.1.2
no Tls.1.1
Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

www.vl-tokyo.co.jp

3.162.79.15

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

supported

www.vl-tokyo.co.jp

3.162.79.15

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=www.vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
	3	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

www.vl-tokyo.co.jp

3.162.79.37

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

www.vl-tokyo.co.jp

3.162.79.37

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=www.vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
	3	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

www.vl-tokyo.co.jp

3.162.79.40

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

www.vl-tokyo.co.jp

3.162.79.40

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=www.vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
	3	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

www.vl-tokyo.co.jp

3.162.79.123

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

www.vl-tokyo.co.jp

3.162.79.123

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=www.vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
	3	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

www.vl-tokyo.co.jp

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

www.vl-tokyo.co.jp

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=www.vl-tokyo.co.jp
	2	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
	3	CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, C=US, ST=New Jersey

182.16.226.147

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

182.16.226.147

443

Certificate/chain invalid and wrong name

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2

Self signed certificate		1	CN=Plesk, O=Plesk, L=Schaffhausen, C=CH, emailAddress=info@plesk.com

9. Certificates

CN=vl-tokyo.co.jp

02.04.2024

02.07.2024
97 days expired

vl-tokyo.co.jp - 1 entry

CN=vl-tokyo.co.jp

02.04.2024

02.07.2024
97 days expired

vl-tokyo.co.jp - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	00B162BAA7BB256FFD26AA735AD8214F44
Thumbprint:	DB2FBBE922F2A38BE562CBFC1612E2A99DDD30AB
SHA256 / Certificate:	mcM4Ga4X6Kf915YvTr+DUTq8FnD60SpWdQ5FTifP3nE=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	cf14c5b9046e0dbd677f24ddd2ebb4e847cf13a2a500cb789d2df5981f6aefb8
SHA256 hex / Subject Public Key Information (SPKI):	cf14c5b9046e0dbd677f24ddd2ebb4e847cf13a2a500cb789d2df5981f6aefb8 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://zerossl.ocsp.sectigo.com
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=vl-tokyo.co.jp

02.04.2024

02.07.2024
97 days expired

vl-tokyo.co.jp - 1 entry

CN=vl-tokyo.co.jp

02.04.2024

02.07.2024
97 days expired

vl-tokyo.co.jp - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	00B162BAA7BB256FFD26AA735AD8214F44
Thumbprint:	DB2FBBE922F2A38BE562CBFC1612E2A99DDD30AB
SHA256 / Certificate:	mcM4Ga4X6Kf915YvTr+DUTq8FnD60SpWdQ5FTifP3nE=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	cf14c5b9046e0dbd677f24ddd2ebb4e847cf13a2a500cb789d2df5981f6aefb8
SHA256 hex / Subject Public Key Information (SPKI):	cf14c5b9046e0dbd677f24ddd2ebb4e847cf13a2a500cb789d2df5981f6aefb8 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://zerossl.ocsp.sectigo.com
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	6C55ABDBD00792C79D070CD8119ED6BF
Thumbprint:	C81A8BD1F9CF6D84C525F378CA1D3F8C30770E34
SHA256 / Certificate:	IazB29aUT5rBjHgstcMo1sKCHGtjcx+juJh/ViXeig0=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SHA256 hex / Subject Public Key Information (SPKI):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://ocsp.usertrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	6C55ABDBD00792C79D070CD8119ED6BF
Thumbprint:	C81A8BD1F9CF6D84C525F378CA1D3F8C30770E34
SHA256 / Certificate:	IazB29aUT5rBjHgstcMo1sKCHGtjcx+juJh/ViXeig0=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SHA256 hex / Subject Public Key Information (SPKI):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://ocsp.usertrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

01.02.2010

19.01.2038
expires in 4852 days

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

01.02.2010

19.01.2038
expires in 4852 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	01FD6D30FCA3CA51A81BBC640E35032D
Thumbprint:	2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E
SHA256 / Certificate:	55PJsC/YqhPiHDEiisywgRlkO3SciYlksXRtRsPUy9I=
SHA256 hex / Cert (DANE * 0 1):	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SHA256 hex / PublicKey (DANE * 1 1):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

12.03.2019

01.01.2029
expires in 1547 days

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

12.03.2019

01.01.2029
expires in 1547 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	3972443AF922B751D7D36C10DD313595
Thumbprint:	D89E3BD43D5D909B47A18977AA9D5CE36CEE184C
SHA256 / Certificate:	aLnHYSGaWx8BMXhEdGZdthu9sQngDwXKn3QkTuX19Ss=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.comodoca.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB

01.01.2004

01.01.2029
expires in 1547 days

CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB

01.01.2004

01.01.2029
expires in 1547 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	01
Thumbprint:	D1EB23A46D17D68FD92564C2F1F1601764D8E349
SHA256 / Certificate:	16eg+11+JzHXcelITrze9x1fDD4KKUh4K8g+4OppnvQ=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
SHA256 hex / Subject Public Key Information (SPKI):	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=www.vl-tokyo.co.jp

23.02.2024

24.05.2024
136 days expired

www.vl-tokyo.co.jp - 1 entry

CN=www.vl-tokyo.co.jp

23.02.2024

24.05.2024
136 days expired

www.vl-tokyo.co.jp - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	7BD16495654BA259ECDC60D9CEBF696B
Thumbprint:	9A25C42437A1F0829FB32B22750384DEF7D10745
SHA256 / Certificate:	x+xlrOlPiWglgEwzIQjTDsCT6B8NhaUwTFHxk8Dd/LU=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	16e83291ef61f5f395950c96f4919b248d12a25a73be0e1d5a6c08d7ae199b44
SHA256 hex / Subject Public Key Information (SPKI):	16e83291ef61f5f395950c96f4919b248d12a25a73be0e1d5a6c08d7ae199b44 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://zerossl.ocsp.sectigo.com
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=www.vl-tokyo.co.jp

23.02.2024

24.05.2024
136 days expired

www.vl-tokyo.co.jp - 1 entry

CN=www.vl-tokyo.co.jp

23.02.2024

24.05.2024
136 days expired

www.vl-tokyo.co.jp - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	7BD16495654BA259ECDC60D9CEBF696B
Thumbprint:	9A25C42437A1F0829FB32B22750384DEF7D10745
SHA256 / Certificate:	x+xlrOlPiWglgEwzIQjTDsCT6B8NhaUwTFHxk8Dd/LU=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	16e83291ef61f5f395950c96f4919b248d12a25a73be0e1d5a6c08d7ae199b44
SHA256 hex / Subject Public Key Information (SPKI):	16e83291ef61f5f395950c96f4919b248d12a25a73be0e1d5a6c08d7ae199b44 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://zerossl.ocsp.sectigo.com
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	6C55ABDBD00792C79D070CD8119ED6BF
Thumbprint:	C81A8BD1F9CF6D84C525F378CA1D3F8C30770E34
SHA256 / Certificate:	IazB29aUT5rBjHgstcMo1sKCHGtjcx+juJh/ViXeig0=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SHA256 hex / Subject Public Key Information (SPKI):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://ocsp.usertrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT

30.01.2020

30.01.2030
expires in 1941 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	6C55ABDBD00792C79D070CD8119ED6BF
Thumbprint:	C81A8BD1F9CF6D84C525F378CA1D3F8C30770E34
SHA256 / Certificate:	IazB29aUT5rBjHgstcMo1sKCHGtjcx+juJh/ViXeig0=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SHA256 hex / Subject Public Key Information (SPKI):	47785c30e006c34585cedb86dac913a1da07a7c20689ddd083adc29fb6146283
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://ocsp.usertrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

01.02.2010

19.01.2038
expires in 4852 days

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

01.02.2010

19.01.2038
expires in 4852 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	01FD6D30FCA3CA51A81BBC640E35032D
Thumbprint:	2B8F1B57330DBBA2D07A6C51F70EE90DDAB9AD8E
SHA256 / Certificate:	55PJsC/YqhPiHDEiisywgRlkO3SciYlksXRtRsPUy9I=
SHA256 hex / Cert (DANE * 0 1):	e793c9b02fd8aa13e21c31228accb08119643b749c898964b1746d46c3d4cbd2
SHA256 hex / PublicKey (DANE * 1 1):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

12.03.2019

01.01.2029
expires in 1547 days

CN=USERTrust RSA Certification Authority, O=The USERTRUST Network, L=Jersey City, S=New Jersey, C=US

12.03.2019

01.01.2029
expires in 1547 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	3972443AF922B751D7D36C10DD313595
Thumbprint:	D89E3BD43D5D909B47A18977AA9D5CE36CEE184C
SHA256 / Certificate:	aLnHYSGaWx8BMXhEdGZdthu9sQngDwXKn3QkTuX19Ss=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SHA256 hex / Subject Public Key Information (SPKI):	c784333d20bcd742b9fdc3236f4e509b8937070e73067e254dd3bf9c45bf4dde
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.comodoca.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB

01.01.2004

01.01.2029
expires in 1547 days

CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB

01.01.2004

01.01.2029
expires in 1547 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	01
Thumbprint:	D1EB23A46D17D68FD92564C2F1F1601764D8E349
SHA256 / Certificate:	16eg+11+JzHXcelITrze9x1fDD4KKUh4K8g+4OppnvQ=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
SHA256 hex / Subject Public Key Information (SPKI):	bd153ed7b0434f6886b17bce8bbe84ed340c7132d702a8f4fa318f756ecbd6f3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

E=info@plesk.com, CN=Plesk, O=Plesk, L=Schaffhausen, C=CH

14.05.2018

14.05.2019
1973 days expired

E=info@plesk.com, CN=Plesk, O=Plesk, L=Schaffhausen, C=CH

14.05.2018

14.05.2019
1973 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	5AF95691
Thumbprint:	A46F3E12FB1E6861E031B3A9B109528A75999D47
SHA256 / Certificate:	fxk6frBGQiH1+X/sUSFRZ+FRKO3WWxOxhZ0IC05Quhg=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	61e2911229eed80af9b6652b99631f89703bb2dd368074f5213a4b6ab4d2f7dc
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuer				last 7 days	active	num Certs
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT				0	0	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
7048086402 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2024-04-02 00:00:00	2024-07-01 23:59:59	vl-tokyo.co.jp - 1 entries
6809226430 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2024-02-23 00:00:00	2024-05-23 23:59:59	www.vl-tokyo.co.jp - 1 entries

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT				0	0	5

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12572410718 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2024-04-01 22:00:00	2024-07-01 21:59:59	vl-tokyo.co.jp 1 entries
12170470455 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2024-02-22 23:00:00	2024-05-23 21:59:59	www.vl-tokyo.co.jp 1 entries
11556678176 precert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2023-12-24 23:00:00	2024-03-24 22:59:59	www.vl-tokyo.co.jp 1 entries
11503471467 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2023-12-18 23:00:00	2024-03-18 22:59:59	vl-tokyo.co.jp, www.vl-tokyo.co.jp 2 entries
10907837958 leaf cert	CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT	2023-10-25 22:00:00	2024-01-24 22:59:59	www.vl-tokyo.co.jp 1 entries

11. Html-Content - Entries

Summary

							Subresource Integrity (SRI)
Domainname	HtmlElement	rel/property	∑	∑ size	∑ problems	∑ int.	∑ ext.	∑ Origin poss.	∑ SRI ParseErrors	∑ SRI valid	∑ SRI missing
https://www.vl-tokyo.co.jp/ 3.162.79.15	a		27		0			0	0	0
	iframe		1		0			0	0	0
	img		9	216,707 Bytes	0	9	0	0	0	0
	link	stylesheet	6		1	4	2	2	0	0	-2
	meta	other	5		0			0	0	0
	script		4		0	4	0	0	0	0
https://www.vl-tokyo.co.jp/ 3.162.79.37	a		27		0			0	0	0
	iframe		1		0			0	0	0
	img		9	216,707 Bytes	0	9	0	0	0	0
	link	stylesheet	6		1	4	2	2	0	0	-2
	meta	other	5		0			0	0	0
	script		4		0	4	0	0	0	0
https://www.vl-tokyo.co.jp/ 3.162.79.40	a		27		0			0	0	0
	iframe		1		0			0	0	0
	img		9	216,707 Bytes	0	9	0	0	0	0
	link	stylesheet	6		1	4	2	2	0	0	-2
	meta	other	5		0			0	0	0
	script		4		0	4	0	0	0	0
https://www.vl-tokyo.co.jp/ 3.162.79.123	a		27		0			0	0	0
	iframe		1		0			0	0	0
	img		9	216,707 Bytes	0	9	0	0	0	0
	link	stylesheet	6		1	4	2	2	0	0	-2
	meta	other	5		0			0	0	0
	script		4		0	4	0	0	0	0

Details

Domainname

Html-Element

name/equiv/ property/rel

href/src/content

HttpStatus

msg

∑

Status

3.162.79.15

/access.html

/careers.html

/en.html

/en/en_legal_update.html

/information_security.html

/news.html

/privacy.html

/service.html

/sitemap.html

/team.html

https://www.vl-tokyo.co.jp/en/en_legal_update.html

https://www.vl-tokyo.co.jp/news/chambers_asia-pacific_2024.html

https://www.vl-tokyo.co.jp/news/new_partner_2023.html

mailto:contact@vl-tokyo.co.jp

iframe

src

https://www.googletagmanager.com/ns.html?id=GTM-P9TL2QX

img

src

/dcms_media/image/common/logo.png

200

alt: Vanguard Tokyo法律事務所

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 52028 Bytes

img

src

/dcms_media/image/top_language_img.png

200

alt: Language

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 4331 Bytes

img

src

/dcms_media/image/top_lawyers_img.png

200

alt: 弁護士紹介

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 12920 Bytes

img

src

/dcms_media/image/top_main_bg.jpg

200

no alt-Attribute

image/jpeg
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 63905 Bytes

img

src

/dcms_media/image/top_main_title01.png

200

alt: Vanguard Lawyers Tokyo

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 11373 Bytes

img

src

/dcms_media/image/top_mainimage_sp.jpg

200

no alt-Attribute

image/jpeg
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 51472 Bytes

img

src

/dcms_media/image/top_news_img.png

200

alt: News

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 3654 Bytes

img

src

/dcms_media/image/top_scroll_img.png

200

alt: Scroll

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 4135 Bytes

img

src

/dcms_media/image/top_service_img.png

200

alt: 取り扱い業務

image/png
missing X-Content-Type-Options nosniff

No Cache-Control header

No Compression - 12889 Bytes

link

stylesheet

//fonts.googleapis.com/css?family=Hind:400,500,600,700|Josefin+Sans

200

text/css; charset=utf-8
X-Content-Type-Options nosniff found

283 Bytes

Server-Header Access-Control-Allow-Origin: *

Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-yiqi7B8rcFNttgC/uBluHUzErcKxY6ZDWHi5eaJZIPc=
sha384-BUnU6RbRMN5WVw/LJOGa33xRbYYDWUfcVaPtIkoWY7Bj2mQI8/bWSTu8RiwTsrfP
sha512-p1ELNKz5H+zzF+YKR478Bvj3dg3XreUc3L4VKDNrX+xXHbpreDj3Up49x6/e4dMOIks4l+7bI7asi9TVx5ZQ1g==

Content loaded via url("...")

https://fonts.gstatic.com/s/hind/v16/5aU19_a8oxmIfJpbERySiA.ttf

https://fonts.gstatic.com/s/hind/v16/5aU19_a8oxmIfLZcERySiA.ttf

https://fonts.gstatic.com/s/hind/v16/5aU19_a8oxmIfNJdERySiA.ttf

https://fonts.gstatic.com/s/hind/v16/5aU69_a8oxmIdGl4AQ.ttf

https://fonts.gstatic.com/s/josefinsans/v32/Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf

link

stylesheet

//fonts.googleapis.com/earlyaccess/notosansjapanese.css

200

text/css; charset=utf-8
X-Content-Type-Options nosniff found

Compression required: 362 Bytes

Server-Header Access-Control-Allow-Origin: *

Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-KLLaq6NM+Bos/ME4f4tkOXC5khfUvzjYGZjxiBco0lA=
sha384-Wz0GkrW3XFZuU5xW5nAqvhykOJBGnYoKkvXVJs8FebAx9oo/jXYQnn0XyUJZ4wgH
sha512-iTpKNZiS5YYjo6eRsB6l+NwvwlSlBFgA3hJPaykD0tvULZkkv10tLjmb9bBNC/bDt1fq9wg053BSxMH1+gyx2Q==

Content loaded via url("...")

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Black.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Black.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Black.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Bold.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Bold.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Bold.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-DemiLight.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-DemiLight.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-DemiLight.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Light.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Light.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Light.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Medium.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Medium.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Medium.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Regular.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Regular.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Regular.woff2

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Thin.otf

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Thin.woff

//fonts.gstatic.com/ea/notosansjapanese/v6/NotoSansJP-Thin.woff2

link

stylesheet

/dcms_media/css/base.css

200

http-link, change to https

text/css
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 3276 Bytes

local SRI possible, possible hash-values:

sha256-s2lSoG7XRSbG9ym+eWvoGdecVYT5P+W0Yv45Yrvltsg=
sha384-tKn+2AmPErakHpp6+0s6Lcl8hjpsSXluZywr3WsBKwC1PZ+baG5Pogw/Edt43Dgo
sha512-xkFCGJdKsIvHGXFziSAiEJPBHRgpaq5GYeRVgAUAiLHZPrRHCbYosYRM/yXiGYyUYPuNT/YXOTT1LiWLyS1cXA==

Content loaded via url("...")

http://fonts.googleapis.com/earlyaccess/notosansjp.css

link

stylesheet

/dcms_media/css/common.css

200

text/css
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 3702 Bytes

local SRI possible, possible hash-values:

sha256-q+u2tfLg6aTRIKsd8m+f/miqtyFokvSN8y6HfsFARD4=
sha384-ypjrtiM31XoiSH0mu8ui/s+qQTaK7vEGNfcJPX9NeU+y5HBwlHzx5dbY20gWJhHC
sha512-kU3LqBNeUAQBNYSxZmMsLHdMdRtLmdkkQun0N01p24zx2RknOYYtd8sabeyFGdPUIVMUignL136xCdYb3ZSLPg==

link

stylesheet

/dcms_media/css/module.css

200

text/css
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 7897 Bytes

local SRI possible, possible hash-values:

sha256-w/lZygCcER5kOphuGLJpNjStFGCyAbxkorQkJv2XVSc=
sha384-/yau4VmFXXRK79yoKehXyQuOKMP0DUs+ePESCvPqNvRxGBK3O56jrFdm26OFloGh
sha512-UChhv9qC8jMkf2hzXwlG9VQY+bm1krP3WWee1xK/xEO+BpNfemUEm5TyID1tfy/fy+hdJqHORzCRnzvJz/6yyQ==

link

stylesheet

/dcms_media/css/top.css

200

text/css
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 3528 Bytes

local SRI possible, possible hash-values:

sha256-gecxUZt8IdlxJng4GqjXOknZxgklVkwLwVMFFd2RAXc=
sha384-S+ZS1ch6dMzmAx9bM6VHybmP89a5iqws3sI3ZzUyhKAJ9jgkyf9V7z9347PRMYj4
sha512-THsxVOXE5bkwTA/UvnAdwB64dE+yYfEji3OPaJO9sLFgYrq1mo8yxTS1Z7+IwgJwZ2lbRTGBlfW6bi3R97OuNQ==

meta

charset

UTF-8

meta

description

Vanguard Tokyo法律事務所は、国内訴訟と労働分野、国内の危機管理や調査対応、そして金融規制に関わる業務を取り扱っている法律事務所です。

meta

google-site-verification

FdMa3G8e8Wxy7qOXb78Dex3lmunVsNuC6P4BjYaSkOA

meta

keywords

Vanguard Tokyo 法律事務所,Vanguard Tokyo法律事務所,弁護士紹介,Vanguard Tokyo合同会社,国際弁護,岡田和樹,山川亜紀子,一般民事,商事案件,労働案件

meta

viewport

width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1

script

src

/dcms_media/js/jquery.biggerlink.target.js

200

Missing defer / async attribute.

application/javascript
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 754 Bytes

local SRI possible, possible hash-values:

sha256-epjwfceMK6aaNhUGr+lETTteT1zle03PHVtclJIO95c=
sha384-ygWMQRrWAJKLsKtZ2z/ru+IF17r1Y35HvowtRluVpETQZqFwcGr7mclDbOKMDNTX
sha512-XK6NcCiWccMynWlNHuCq+yFdPAzxa8qcDGo0u8rhB7OHrMJuB20zG4b9LzB27pc7BGQcucARZ+CEEKXJgB+qBg==

script

src

/dcms_media/js/jquery.matchHeight-min.js

200

Missing defer / async attribute.

application/javascript
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 990 Bytes

local SRI possible, possible hash-values:

sha256-xPyF8qqcIJptRhflEPK4MzoSs8KPdcouQwEpsFSjIc4=
sha384-HX/6qvidx1GCoPnXOkfnqbvozny5sw6SmSjbysdftwT9qmCuB7XLW/hfuJnQ7OOV
sha512-smrdB1GW13mvivBwjaFR/6Ish1zu/mZNACCRJ/eFeN1bAwvPolyq87+WzVfTNYPHojE69fcg9LBJYoiKa69oRg==

script

src

/dcms_media/js/jquery-1.11.1.min.js

200

Missing defer / async attribute.

application/javascript
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 33356 Bytes

local SRI possible, possible hash-values:

sha256-VAvG3sHdS5LqTT+5A/aeq/bZGa/Uj04xKxY8KM/w9EE=
sha384-UM1JrZIpBwVf5jj9dTKVvGiiZPZTLVoq4sfdvIe9SBumsvCuv6AHDNtEiIb5h1kU
sha512-nhY06wKras39lb9lRO76J4397CH1XpRSLfLJSftTeo3+q2vP7PaebILH9TqH+GRpnOhfAGjuYMVmVTOZJ+682w==

script

src

/dcms_media/js/scrolltopcontrol.js

200

Missing defer / async attribute.

application/javascript
missing X-Content-Type-Options nosniff

No Cache-Control - header

Compression required: 1610 Bytes

local SRI possible, possible hash-values:

sha256-ODf7Bt3DUGL7b40oer4gnRrov/kQmId4f5/XBcn62KE=
sha384-/4BkLoUdakrEHGo54QwyvYIH4tADSZkr3Ml8ThJJSWRSLnaTM5DIyWkJYlMAFvRU
sha512-lePvdTpC4Eo11VNC1kXSoYXoaB2E14BsTO1asMlzL0xvCj317uLxw+mI+lCOej5dbMAM9fAV5Uq1+rvS2ikuzQ==