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

0 in Queue, 0 of max. 8 Checks (01:20:27)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

N

 

No trusted Certificate

 

Checked:
18.09.2020 10:06:16

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
persona.servier.com.cn

Server failure
yes
2
0
www.persona.servier.com.cn

Name Error
yes
1
0
persona.servier.com.cn
A
139.217.112.174
Beijing/China (CN) - Microsoft (China) Co
No Hostname found
no


*.servier.com.cn
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.persona.servier.com.cn
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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 46594, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2020, 00:00:00 +, Signature-Inception: 09.09.2020, 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: cn

cn
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 57724, DigestType 2 and Digest XQQjYz6ySkmb54qiLRwMm6NiGP9J/ZWkzfGkrZfGcEQ=






1 RRSIG RR to validate DS RR found






RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2020, 05:00:00 +, Signature-Inception: 18.09.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 38388, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2020, 01:48:55 +, Signature-Inception: 08.09.2020, 00:48:55 +, KeyTag 38388, Signer-Name: cn






RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2020, 01:48:55 +, Signature-Inception: 08.09.2020, 00:48:55 +, KeyTag 57724, Signer-Name: cn






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






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






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



Zone: com.cn

com.cn
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 46387, DigestType 2 and Digest 32myz+ZtY6MGhCPmdvHX1A4I4oaAZOxwfKv3hMAGlSs=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com.cn., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2020, 01:48:55 +, Signature-Inception: 08.09.2020, 00:48:55 +, KeyTag 38388, Signer-Name: cn






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 43326, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com.cn., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2020, 01:57:50 +, Signature-Inception: 08.09.2020, 00:57:50 +, KeyTag 43326, Signer-Name: com.cn






RRSIG-Owner com.cn., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2020, 01:57:50 +, Signature-Inception: 08.09.2020, 00:57:50 +, KeyTag 46387, Signer-Name: com.cn






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






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






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



Zone: servier.com.cn

servier.com.cn
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 "qrthulghb4377tstcurh4aif9dpmonbj" between the hashed NSEC3-owner "qdg8cf16pfulbmfjq3leqmjip003h0vo" and the hashed NextOwner "r493hmg3gtcj3v809gcnsmaqg74c467k". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner qdg8cf16pfulbmfjq3leqmjip003h0vo.com.cn., Algorithm: 8, 3 Labels, original TTL: 21600 sec, Signature-expiration: 08.10.2020, 03:59:37 +, Signature-Inception: 08.09.2020, 02:59:37 +, KeyTag 43326, Signer-Name: com.cn






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "gice14dntmdn31g43augvrktkalvb8qc" as Owner. That's the Hash of "com.cn" with the NextHashedOwnerName "gkm1khvfsnslutjubf7jhhpg9f17brfq". So that domain name is the Closest Encloser of "servier.com.cn". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner gice14dntmdn31g43augvrktkalvb8qc.com.cn., Algorithm: 8, 3 Labels, original TTL: 21600 sec, Signature-expiration: 08.10.2020, 03:44:02 +, Signature-Inception: 08.09.2020, 02:44:02 +, KeyTag 43326, Signer-Name: com.cn






0 DNSKEY RR found









Zone: persona.servier.com.cn

persona.servier.com.cn
0 DS RR in the parent zone found



Zone: www.persona.servier.com.cn

www.persona.servier.com.cn
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.persona.servier.com.cn
•  ns1.sfn.cn

servier.com.cn
•  ns1.sfn.cn
210.72.13.121
Shanghai/China (CN) - Computer Network Information Center

• 
210.72.13.124
Shanghai/China (CN) - Computer Network Information Center

•  ns2.sfn.cn
112.124.124.53
Hangzhou/Zhejiang/China (CN) - Addresses CNNIC

• 
124.16.31.122
Beijing/China (CN) - Computer Network Information Center
com.cn
•  a.dns.cn
203.119.25.1
Beijing/China (CN) - CNNIC		•

• 
2001:dc7::1
Beijing/China (CN) - China Internet Network Information Center		•

•  b.dns.cn
203.119.26.1
Beijing/China (CN) - CNNIC		•

•  c.dns.cn
203.119.27.1
Beijing/China (CN) - China Internet Network Information Center		•

•  cns.cernet.net
103.137.60.44
Haidian/Beijing/China (CN) - China Education and Research Network		•

• 
2001:da8:1:100::44
Haidian/Beijing/China (CN) - China Next Generation Internet CERNET2		•

• 
2001:dd9::44
Haidian/Beijing/China (CN) - China Education and Research Network		•

•  d.dns.cn
203.119.28.1
Beijing/China (CN) - China Internet Network Information Center		•

• 
2001:dc7:1000::1
Beijing/China (CN) - China Internet Network Information Center		•

•  e.dns.cn
203.119.29.1
Beijing/China (CN) - China Internet Network Information Center		•

•  f.dns.cn
195.219.8.90
High Wycombe/England/United Kingdom (GB) - TATA Communications		•

•  g.dns.cn
66.198.183.65
New York/United States (US) - TATA COMMUNICATIONS (AMERICA) INC		•
cn
•  a.dns.cn
•

•  b.dns.cn
•

•  c.dns.cn
•

•  d.dns.cn
•

•  e.dns.cn
•

•  f.dns.cn
•

•  g.dns.cn
•

•  ns.cernet.net
•

 

4. SOA-Entries


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120971
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:2


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120971
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:2


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120972
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:2


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120972
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:2


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120973
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:4


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027120973
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:4


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095450
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095450
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095450
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095552
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:3


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095552
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:3


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095552
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:3


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095553
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095553
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095553
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:1


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095554
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:7


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095554
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:7


Domain:com.cn
Zone-Name:com.cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2027095554
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:7


Domain:servier.com.cn
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:servier.com.cn
Zone-Name:servier.com.cn
Primary:ns1.sfn.cn
Mail:root.ns1.sfn.cn
Serial:2009181551
Refresh:600
Retry:120
Expire:604800
TTL:7200
num Entries:2


Domain:servier.com.cn
Zone-Name:servier.com.cn
Primary:ns1.sfn.cn
Mail:root.ns1.sfn.cn
Serial:2009181555
Refresh:600
Retry:120
Expire:604800
TTL:7200
num Entries:1


Domain:www.persona.servier.com.cn
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://persona.servier.com.cn, address used: https://persona.servier.com.cn/, Screenshot created 2020-09-18 10:13:02 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

460 milliseconds

 

Screenshot mobile - https://persona.servier.com.cn/
Mobil + Landscape (732px x 412px)

 

830 milliseconds

 

Screenshot mobile landscape - https://persona.servier.com.cn/
Screen (1280px x 1680px)

 

1321 milliseconds

 

Screenshot Desktop - https://persona.servier.com.cn/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.2, ECDHE_RSA with P-256, and AES_128_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://persona.servier.com.cn/
139.217.112.174
-14


9.997
T
Timeout - The operation has timed out

• https://persona.servier.com.cn/
139.217.112.174
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/858		404

Html is minified: 340.35 %
Other inline scripts (∑/total): 0/0		5.734
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 13)
404 Not Found
Date: Fri, 18 Sep 2020 08:12:17 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.2.33
X-Powered-By: PHP/7.2.33
Cache-Control: no-cache, private
Content-Length: 1552
Connection: close
Content-Type: text/html; charset=UTF-8

• http://persona.servier.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
139.217.112.174
-14


10.000
T
Timeout - The operation has timed out
Visible Content:

• https://139.217.112.174/
139.217.112.174
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/858		404

Html is minified: 340.35 %
Other inline scripts (∑/total): 0/0		5.920
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 13)
404 Not Found
Date: Fri, 18 Sep 2020 08:12:35 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.2.33
X-Powered-By: PHP/7.2.33
Cache-Control: no-cache, private
Content-Length: 1552
Connection: close
Content-Type: text/html; charset=UTF-8

 

7. Comments


1. General Results, most used to calculate the result

Aname "persona.servier.com.cn" is subdomain, public suffix is ".com.cn", top-level-domain is ".cn", top-level-domain-type is "country-code", Country is China, tld-manager is "China Internet Network Information Center (CNNIC)", num .cn-domains preloaded: 486 (complete: 131120)
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://persona.servier.com.cn/ 139.217.112.174
404

Missing HSTS-Header
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Mhttps://persona.servier.com.cn/ 139.217.112.174
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://139.217.112.174/ 139.217.112.174
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://persona.servier.com.cn/ 139.217.112.174
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://139.217.112.174/ 139.217.112.174
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
XFatal error: Nameserver doesn't support TCP connection: ns1.sfn.cn / 210.72.13.121: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns1.sfn.cn / 210.72.13.124: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.sfn.cn / 112.124.124.53: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns2.sfn.cn / 124.16.31.122: Timeout

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
AInfo:: 7 Queries complete, 5 with IPv6, 0 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.
AInfo:: 2 different Name Servers found: ns1.sfn.cn, ns2.sfn.cn, 2 Name Servers included in Delegation: ns1.sfn.cn, ns2.sfn.cn, 2 Name Servers included in 1 Zone definitions: ns1.sfn.cn, ns2.sfn.cn, 1 Name Servers listed in SOA.Primary: ns1.sfn.cn.
AGood: Only one SOA.Primary Name Server found.: ns1.sfn.cn.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.sfn.cn.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 112., 124., 210., 3 different subnets (first two Bytes): 112.124., 124.16., 210.72., 3 different subnets (first three Bytes): 112.124.124., 124.16.31., 210.72.13.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.sfn.cn: 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.
Nameserver doesn't pass all EDNS-Checks: ns2.sfn.cn / 112.124.124.53: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://persona.servier.com.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 139.217.112.174
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: 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://persona.servier.com.cn/ 139.217.112.174
404
5.734 seconds
Warning: 404 needs more then one second
https://139.217.112.174/ 139.217.112.174
404
5.920 seconds
Warning: 404 needs more then one second
ADuration: 412626 milliseconds, 412.626 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
persona.servier.com.cn
139.217.112.174
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
persona.servier.com.cn
139.217.112.174
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
 Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate

1CN=azvmcnn212.internal.chinacloudapp.cn, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, C=--, emailAddress=root@azvmcnn212.internal.chinacloudapp.cn


139.217.112.174
139.217.112.174
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

139.217.112.174
139.217.112.174
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
Tls.1.1
Tls.1.0
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
Tls.1.1
Tls.1.0
Self signed certificate

1CN=azvmcnn212.internal.chinacloudapp.cn, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, C=--, emailAddress=root@azvmcnn212.internal.chinacloudapp.cn

 

9. Certificates

1.
1.
E=root@azvmcnn212.internal.chinacloudapp.cn, CN=azvmcnn212.internal.chinacloudapp.cn, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, S=SomeState, C=--
25.08.2020
25.08.2021
1665 days expired
1.
1.
E=root@azvmcnn212.internal.chinacloudapp.cn, CN=azvmcnn212.internal.chinacloudapp.cn, OU=SomeOrganizationalUnit, O=SomeOrganization, L=SomeCity, S=SomeState, C=--
25.08.2020

25.08.2021
1665 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:4C8B
Thumbprint:C775D24CCBD87ADE19F208A8E8F74D76D5CC225C
SHA256 / Certificate:t/eFR5l896fJJjjjslXEbVbHSOr2SUjthWdMHghH544=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2c85356f76117460b1c76d35cfff474faa107a50fb01f782e0fe8e27304d1dd2
SHA256 hex / Subject Public Key Information (SPKI):2c85356f76117460b1c76d35cfff474faa107a50fb01f782e0fe8e27304d1dd2
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:


UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


 

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found

 

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.sfn.cn, ns2.sfn.cn

 

QNr.DomainTypeNS used
1
cn
NS
e.root-servers.net (2001:500:a8::e)

Answer: a.dns.cn, b.dns.cn, c.dns.cn, d.dns.cn, e.dns.cn, f.dns.cn, g.dns.cn, ns.cernet.net
2
ns1.sfn.cn
NS
a.dns.cn (2001:dc7::1)

Answer: vip1.sfndns.cn, vip2.sfndns.cn

Answer: vip1.sfndns.cn
121.12.104.113, 124.16.31.2, 218.98.111.113, 2400:dd01:3019::180, 2404:da80::1:19d, 27.152.186.196

Answer: vip2.sfndns.cn
119.167.180.168, 124.16.31.3, 183.253.57.196, 2400:dd01:3019::181, 240e:ff:9000:1100::19d, 42.157.225.231
3
ns2.sfn.cn
NS
a.dns.cn (2001:dc7::1)

Answer: vip1.sfndns.cn, vip2.sfndns.cn

Answer: vip1.sfndns.cn
121.12.104.113, 124.16.31.2, 218.98.111.113, 2400:dd01:3019::180, 2404:da80::1:19d, 27.152.186.196

Answer: vip2.sfndns.cn
119.167.180.168, 124.16.31.3, 183.253.57.196, 2400:dd01:3019::181, 240e:ff:9000:1100::19d, 42.157.225.231
5
ns1.sfn.cn: No AAAA record found
AAAA
vip1.sfndns.cn (2400:dd01:3019::180)
7
ns2.sfn.cn: No AAAA record found
AAAA
vip1.sfndns.cn (2400:dd01:3019::180)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
servier.com.cn
0

no CAA entry found
1
0
com.cn
0

no CAA entry found
1
0
cn
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
servier.com.cn

ok
1
0
_acme-challenge.persona.servier.com.cn.servier.com.cn

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=5c08ab23-8b2d-4dd8-91e7-f1de29720242

 

Last Result: https://check-your-website.server-daten.de/?q=persona.servier.com.cn - 2020-09-18 10:06:16

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=persona.servier.com.cn" target="_blank">Check this Site: persona.servier.com.cn</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=persona.servier.com.cn

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions