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

0 in Queue, 1 of max. 8 Checks (21:35:58)
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 |

 

O

 

old / weak connection

 

Checked:
29.11.2024 12:42:40

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cn-modelservice-t-api.trafficmanager.cn
CNAME
cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn
yes
1
0

A
40.72.117.125
Huangpu Qu/Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd
No Hostname found
yes


www.cn-modelservice-t-api.trafficmanager.cn

Name Error
yes
1
0
*.trafficmanager.cn
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cn-modelservice-t-api.trafficmanager.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 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

cn
1 DS RR in the parent zone found






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






2 RRSIG RR to validate DS RR found






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






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61050 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: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, KeyTag 38388, Signer-Name: cn






RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, 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: trafficmanager.cn

trafficmanager.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 "lvqkdddugbrpg5f0enkfdc21fob8k07u" between the hashed NSEC3-owner "lvn3652rfq8rn5f8ifj3ofjvl03plviv" and the hashed NextOwner "m08mfp47ajk38ce4dlj2bnjtol1npkj8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner lvn3652rfq8rn5f8ifj3ofjvl03plviv.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, KeyTag 38388, Signer-Name: cn






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3qdaqa092ee5belp64a74ebnb8j53d7e" as Owner. That's the Hash of "cn" with the NextHashedOwnerName "3qm14fq32f1cjftp8d3j5bctnp5bielo". So that domain name is the Closest Encloser of "trafficmanager.cn". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3qdaqa092ee5belp64a74ebnb8j53d7e.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, KeyTag 38388, Signer-Name: cn






0 DNSKEY RR found









Zone: cn-modelservice-t-api.trafficmanager.cn

cn-modelservice-t-api.trafficmanager.cn
0 DS RR in the parent zone found



Zone: www.cn-modelservice-t-api.trafficmanager.cn

www.cn-modelservice-t-api.trafficmanager.cn
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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

cn
1 DS RR in the parent zone found






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






2 RRSIG RR to validate DS RR found






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






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61050 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: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, KeyTag 38388, Signer-Name: cn






RRSIG-Owner cn., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, 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: chinacloudapi.cn

chinacloudapi.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 "047qbeba8q9b4gk02onr86jn0c4bg29j" between the hashed NSEC3-owner "044ae6fvacjf33o7qqq5r0tdhr3isf4u" and the hashed NextOwner "04le3toqgkt5932695u8liediv2lpo3k". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 044ae6fvacjf33o7qqq5r0tdhr3isf4u.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 15.12.2024, 05:47:21 +, Signature-Inception: 15.11.2024, 04:47:21 +, KeyTag 38388, Signer-Name: cn






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "3qdaqa092ee5belp64a74ebnb8j53d7e" as Owner. That's the Hash of "cn" with the NextHashedOwnerName "3qm14fq32f1cjftp8d3j5bctnp5bielo". So that domain name is the Closest Encloser of "chinacloudapi.cn". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 3qdaqa092ee5belp64a74ebnb8j53d7e.cn., Algorithm: 8, 2 Labels, original TTL: 21600 sec, Signature-expiration: 12.12.2024, 02:17:42 +, Signature-Inception: 12.11.2024, 01:17:42 +, KeyTag 38388, Signer-Name: cn






0 DNSKEY RR found









Zone: cloudapp.chinacloudapi.cn

cloudapp.chinacloudapi.cn
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: chinaeast2.cloudapp.chinacloudapi.cn

chinaeast2.cloudapp.chinacloudapi.cn
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn

cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn
0 DS RR in the parent zone found






0 DNSKEY RR found







 

3. Name Servers

DomainNameserverNS-IP
www.cn-modelservice-t-api.trafficmanager.cn
•  tm1.dns-tm.cn

trafficmanager.cn
•  tm1.dns-tm.cn
40.73.208.240
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  tm1.edgedns-tm.cn
40.73.212.240
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  tm2.dns-tm.cn
40.73.210.240
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  tm2.edgedns-tm.cn
40.73.214.240
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•
cn
•  a.dns.cn
•

•  b.dns.cn
•

•  c.dns.cn
•

•  d.dns.cn
•

•  e.dns.cn
•

•  ns.cernet.net
•
cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn
•  ns1-04.azure-dns-1.cn
40.73.192.4
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•
chinaeast2.cloudapp.chinacloudapi.cn
•  ns1-04.azure-dns-1.cn
40.73.192.4
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns2-04.azure-dns-1.cn
40.73.194.4
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns3-04.azure-dns-1.cn
40.73.196.4
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns4-04.azure-dns-1.cn
40.73.198.4
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•
cloudapp.chinacloudapi.cn
•  ns1-201.azure-dns-3.cn
40.73.192.201
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•
chinacloudapi.cn
•  ns1-201.azure-dns-3.cn
40.73.192.201
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns2-201.azure-dns-3.cn
40.73.194.201
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns3-201.azure-dns-3.cn
40.73.196.201
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•

•  ns4-201.azure-dns-3.cn
40.73.198.201
Shanghai/China (CN) - Shanghai Blue Cloud Technology Co., Ltd		•
cn
T  a.dns.cn
•

•  b.dns.cn
•

•  c.dns.cn
•

•  d.dns.cn
•

•  e.dns.cn
•

T  ns.cernet.net
•

 

4. SOA-Entries


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


Domain:trafficmanager.cn
Zone-Name:trafficmanager.cn
Primary:tm1.dns-tm.cn
Mail:hostmaster.trafficmanager.cn
Serial:2003080800
Refresh:900
Retry:300
Expire:2419200
TTL:30
num Entries:4


Domain:www.cn-modelservice-t-api.trafficmanager.cn
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:cn
Zone-Name:cn
Primary:a.dns.cn
Mail:root.cnnic.cn
Serial:2032838269
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:2032838270
Refresh:7200
Retry:3600
Expire:2419200
TTL:21600
num Entries:4


Domain:chinacloudapi.cn
Zone-Name:chinacloudapi.cn
Primary:ns1-201.azure-dns-3.cn
Mail:hostmaster.windowsazure.cn
Serial:2013051832
Refresh:1800
Retry:900
Expire:2419200
TTL:300
num Entries:4


Domain:cloudapp.chinacloudapi.cn
Zone-Name:chinacloudapi.cn
Primary:ns1-201.azure-dns-3.cn
Mail:hostmaster.windowsazure.cn
Serial:2013051832
Refresh:1800
Retry:900
Expire:2419200
TTL:300
num Entries:1


Domain:chinaeast2.cloudapp.chinacloudapi.cn
Zone-Name:chinaeast2.cloudapp.chinacloudapi.cn
Primary:ns1-04.azure-dns-1.cn
Mail:ns2.windowsazure.cn
Serial:1
Refresh:900
Retry:300
Expire:604800
TTL:60
num Entries:4


Domain:cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn
Zone-Name:chinaeast2.cloudapp.chinacloudapi.cn
Primary:ns1-04.azure-dns-1.cn
Mail:ns2.windowsazure.cn
Serial:1
Refresh:900
Retry:300
Expire:604800
TTL:60
num Entries:1


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://cn-modelservice-t-api.trafficmanager.cn/
40.72.117.125
308
https://cn-modelservice-t-api.trafficmanager.cn/
Html is minified: 109.33 %
0.517
A
Date: Fri, 29 Nov 2024 11:49:10 GMT
Connection: keep-alive
Location: https://cn-modelservice-t-api.trafficmanager.cn/
Content-Type: text/html
Content-Length: 164

• https://cn-modelservice-t-api.trafficmanager.cn/
40.72.117.125
404


9.250
M
Not Found
Date: Fri, 29 Nov 2024 11:49:11 GMT
Connection: keep-alive
Request-Context: appId=cid-v1:096de5d7-6719-4b8d-85bb-9c3cfb413f3a
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Length: 0

• http://cn-modelservice-t-api.trafficmanager.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
40.72.117.125
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		308
https://cn-modelservice-t-api.trafficmanager.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.33 %
Other inline scripts (∑/total): 0/0		0.260
A
Visible Content:
Date: Fri, 29 Nov 2024 11:49:21 GMT
Connection: keep-alive
Location: https://cn-modelservice-t-api.trafficmanager.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 164

• https://cn-modelservice-t-api.trafficmanager.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


9.620
A
Not Found
Visible Content:
Date: Fri, 29 Nov 2024 11:49:32 GMT
Connection: keep-alive
Request-Context: appId=cid-v1:096de5d7-6719-4b8d-85bb-9c3cfb413f3a
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Length: 0

• https://40.72.117.125/
40.72.117.125
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0		9.007
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Fri, 29 Nov 2024 11:49:22 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html
Content-Length: 146

 

7. Comments


1. General Results, most used to calculate the result

Aname "cn-modelservice-t-api.trafficmanager.cn" is subdomain, public suffix is ".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: 907 (complete: 263653)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: cn-modelservice-t-api.trafficmanager.cn 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: cn-modelservice-t-api.trafficmanager.cn has no ipv6 address.
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: No cookie sent via http.
AGood: every https has a Strict Transport Security Header
AGood: HSTS has includeSubdomains - directive
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
https://40.72.117.125/ 40.72.117.125


Url with incomplete Content-Type - header - missing charset
Ahttp://cn-modelservice-t-api.trafficmanager.cn/ 40.72.117.125
308
https://cn-modelservice-t-api.trafficmanager.cn/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15724800 seconds = 182 days found
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Mhttps://cn-modelservice-t-api.trafficmanager.cn/ 40.72.117.125
404

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

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://40.72.117.125/ 40.72.117.125
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Ocn-modelservice-t-api.trafficmanager.cn / 40.72.117.125 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 14 Cipher Suites without Forward Secrecy found
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 cn-modelservice-t-api.trafficmanager.cn, 1 ip addresses.
BNo _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.cn-modelservice-t-api.trafficmanager.cn

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

Fcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Content-Security-Policy
Critical: Missing Header:
Fcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
X-Content-Type-Options
Critical: Missing Header:
Fcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Referrer-Policy
Critical: Missing Header:
Fcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Permissions-Policy
Critical: Missing Header:
Bcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Cross-Origin-Embedder-Policy
Info: Missing Header
Bcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Cross-Origin-Opener-Policy
Info: Missing Header
Bcn-modelservice-t-api.trafficmanager.cn 40.72.117.125
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 37 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 37 Queries complete, 13 with IPv6, 24 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.
Bad (greater 8):: An average of 9.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: tm1.dns-tm.cn, tm1.edgedns-tm.cn, tm2.dns-tm.cn, tm2.edgedns-tm.cn, 4 Name Servers included in Delegation: tm1.dns-tm.cn, tm1.edgedns-tm.cn, tm2.dns-tm.cn, tm2.edgedns-tm.cn, 4 Name Servers included in 1 Zone definitions: tm1.dns-tm.cn, tm1.edgedns-tm.cn, tm2.dns-tm.cn, tm2.edgedns-tm.cn, 1 Name Servers listed in SOA.Primary: tm1.dns-tm.cn.
AGood: Only one SOA.Primary Name Server found.: tm1.dns-tm.cn.
AGood: SOA.Primary Name Server included in the delegation set.: tm1.dns-tm.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, 1 different subnets (first Byte): 40., 1 different subnets (first two Bytes): 40.73., 4 different subnets (first three Bytes): 40.73.208., 40.73.210., 40.73.212., 40.73.214.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
XNameserver Timeout checking Echo Capitalization: a.dns.cn
XNameserver Timeout checking Echo Capitalization: ns.cernet.net
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: a.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: d.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: d.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: e.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: e.dns.cn: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns.cernet.net: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: tm1.dns-tm.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.
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

AGood: 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.
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://cn-modelservice-t-api.trafficmanager.cn/ 40.72.117.125
404
9.250 seconds
Warning: 404 needs more then one second
https://cn-modelservice-t-api.trafficmanager.cn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
9.620 seconds
Warning: 404 needs more then one second
https://40.72.117.125/ 40.72.117.125
404
9.007 seconds
Warning: 404 needs more then one second
ADuration: 613207 milliseconds, 613.207 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
cn-modelservice-t-api.trafficmanager.cn
40.72.117.125
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
cn-modelservice-t-api.trafficmanager.cn
40.72.117.125
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
SNI required 		Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
SNI required 		Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=cn-modelservice-t-api.trafficmanager.cn


2CN=R10, O=Let's Encrypt, C=US


cn-modelservice-t-api.trafficmanager.cn
cn-modelservice-t-api.trafficmanager.cn
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

cn-modelservice-t-api.trafficmanager.cn
cn-modelservice-t-api.trafficmanager.cn
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=cn-modelservice-t-api.trafficmanager.cn


2CN=R10, O=Let's Encrypt, C=US


40.72.117.125
40.72.117.125
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

40.72.117.125
40.72.117.125
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
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

1CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

 

9. Certificates

1.
1.
CN=cn-modelservice-t-api.trafficmanager.cn
29.11.2024
27.02.2025
expires in 87 days		cn-modelservice-t-api.trafficmanager.cn - 1 entry
1.
1.
CN=cn-modelservice-t-api.trafficmanager.cn
29.11.2024

27.02.2025
expires in 87 days


cn-modelservice-t-api.trafficmanager.cn - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03B4A0D0C2B2DACEA13517B7B2365457F015
Thumbprint:9D6E0EE6B75E0237F88211F37F888331C501F4FE
SHA256 / Certificate:ezE3T2l+wBlk4J4pBHKPNnkhUIKj9GM3MXlMVg2Z0/4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):132334f7e3fa6a3df63a076c22bfe12be8dbd5b85da4940678e5a69251f3424a
SHA256 hex / Subject Public Key Information (SPKI):132334f7e3fa6a3df63a076c22bfe12be8dbd5b85da4940678e5a69251f3424a (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r10.o.lencr.org
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)




2.
CN=R10, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 831 days

2.
CN=R10, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 831 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:4BA85293F79A2FA273064BA8048D75D0
Thumbprint:00ABEFD055F9A9C784FFDEABD1DCDD8FED741436
SHA256 / Certificate:nXw/GqatKy7A1c8eJG+NmubLyf0HVa03u5dLHy+2A/M=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):Error find_SubjectPublicKeyInfo_in_Certificate - no result found
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:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3836 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3836 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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:




2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
26.11.2024
26.11.2025
expires in 359 days		ingress.local - 1 entry
2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
26.11.2024

26.11.2025
expires in 359 days


ingress.local - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:6923F701F1474656D33441E1BE3EBB33
Thumbprint:93ED1AF985B4A5A0DA6B0D1D792B3FD7439B09EF
SHA256 / Certificate:CIA39DrAC+qNq8ysEGMQKJXPmyca2QOiRg0+keaCN2U=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):3e27b2f12b98c347e5dbbd4f733b939783df5ac5a0a0c911553583eea0523c52
SHA256 hex / Subject Public Key Information (SPKI):3e27b2f12b98c347e5dbbd4f733b939783df5ac5a0a0c911553583eea0523c52 (is buggy, ignore the result)
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)


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

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: tm1.dns-tm.cn, tm1.edgedns-tm.cn, tm2.dns-tm.cn, tm2.edgedns-tm.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, ns.cernet.net
2
tm1.dns-tm.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-05.azure-dns-1.cn, ns2-05.azure-dns-1.cn, ns3-05.azure-dns-1.cn, ns4-05.azure-dns-1.cn
3
tm1.edgedns-tm.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-06.azure-dns-1.cn, ns2-06.azure-dns-1.cn, ns3-06.azure-dns-1.cn, ns4-06.azure-dns-1.cn
4
tm2.dns-tm.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-05.azure-dns-1.cn, ns2-05.azure-dns-1.cn, ns3-05.azure-dns-1.cn, ns4-05.azure-dns-1.cn
5
tm2.edgedns-tm.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-06.azure-dns-1.cn, ns2-06.azure-dns-1.cn, ns3-06.azure-dns-1.cn, ns4-06.azure-dns-1.cn
6
ns1-05.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
7
ns2-05.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
8
ns3-05.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
9
ns4-05.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
10
ns1-06.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
11
ns2-06.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
12
ns3-06.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
13
ns4-06.azure-dns-1.cn
NS
a.dns.cn (2001:dc7::1)

Answer: ns1-04.azure-dns-1.cn, ns2-04.azure-dns-1.cn, ns3-04.azure-dns-1.cn, ns4-04.azure-dns-1.cn

Answer: ns1-04.azure-dns-1.cn
40.73.192.4

Answer: ns2-04.azure-dns-1.cn
40.73.194.4

Answer: ns3-04.azure-dns-1.cn
40.73.196.4

Answer: ns4-04.azure-dns-1.cn
40.73.198.4
14
ns1-05.azure-dns-1.cn: 40.73.192.5
A
ns1-04.azure-dns-1.cn (40.73.192.4)
15
ns1-05.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
16
ns2-05.azure-dns-1.cn: 40.73.194.5
A
ns1-04.azure-dns-1.cn (40.73.192.4)
17
ns2-05.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
18
ns3-05.azure-dns-1.cn: 40.73.196.5
A
ns1-04.azure-dns-1.cn (40.73.192.4)
19
ns3-05.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
20
ns4-05.azure-dns-1.cn: 40.73.198.5
A
ns1-04.azure-dns-1.cn (40.73.192.4)
21
ns4-05.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
22
ns1-06.azure-dns-1.cn: 40.73.192.6
A
ns1-04.azure-dns-1.cn (40.73.192.4)
23
ns1-06.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
24
ns2-06.azure-dns-1.cn: 40.73.194.6
A
ns1-04.azure-dns-1.cn (40.73.192.4)
25
ns2-06.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
26
ns3-06.azure-dns-1.cn: 40.73.196.6
A
ns1-04.azure-dns-1.cn (40.73.192.4)
27
ns3-06.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
28
ns4-06.azure-dns-1.cn: 40.73.198.6
A
ns1-04.azure-dns-1.cn (40.73.192.4)
29
ns4-06.azure-dns-1.cn: No AAAA record found
AAAA
ns1-04.azure-dns-1.cn (40.73.192.4)
30
tm1.dns-tm.cn: 40.73.208.240
A
ns1-05.azure-dns-1.cn (40.73.192.5)
31
tm1.dns-tm.cn: No AAAA record found
AAAA
ns1-05.azure-dns-1.cn (40.73.192.5)
32
tm1.edgedns-tm.cn: 40.73.212.240
A
ns1-06.azure-dns-1.cn (40.73.192.6)
33
tm1.edgedns-tm.cn: No AAAA record found
AAAA
ns1-06.azure-dns-1.cn (40.73.192.6)
34
tm2.dns-tm.cn: 40.73.210.240
A
ns1-05.azure-dns-1.cn (40.73.192.5)
35
tm2.dns-tm.cn: No AAAA record found
AAAA
ns1-05.azure-dns-1.cn (40.73.192.5)
36
tm2.edgedns-tm.cn: 40.73.214.240
A
ns1-06.azure-dns-1.cn (40.73.192.6)
37
tm2.edgedns-tm.cn: No AAAA record found
AAAA
ns1-06.azure-dns-1.cn (40.73.192.6)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn
0

no CAA entry found
1
0
cn-modelservice-t-api.trafficmanager.cn



1
0
chinaeast2.cloudapp.chinacloudapi.cn
0

no CAA entry found
1
0
cloudapp.chinacloudapi.cn
0

no CAA entry found
1
0
trafficmanager.cn
0

no CAA entry found
1
0
chinacloudapi.cn
0

no CAA entry found
1
0
cn
0

no CAA entry found
1
0

0

no CAA entry found
2
1

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
trafficmanager.cn

ok
1
0
cn-modelservice-t-api.trafficmanager.cn


1
0
_acme-challenge.cn-modelservice-t-api.trafficmanager.cn

Name Error - The domain name does not exist
1
0
_acme-challenge.cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn

Name Error - The domain name does not exist
1
0
_acme-challenge.cn-modelservice-t-api.trafficmanager.cn.trafficmanager.cn

Name Error - The domain name does not exist
1
0
_acme-challenge.cn-modelservice-t-api.trafficmanager.cn.cn-modelservice-t-api.trafficmanager.cn

Name Error - The domain name does not exist
1
0
_acme-challenge.cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn.cn-communicate-t-tmp.chinaeast2.cloudapp.chinacloudapi.cn

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
SPF
TXT
cn-modelservice-t-api.trafficmanager.cn

32768TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
cn-modelservice-t-api.trafficmanager.cn
40.72.117.125
443
22 Ciphers174.22 sec
14 without, 8 FS
36.36 %
Complete

1
22 Ciphers
22.00 Ciphers/Check		174.22 sec174.22 sec/Check
14 without, 8 FS
36.36 %

Details
DomainIPPortCipher (OpenSsl / IANA)
cn-modelservice-t-api.trafficmanager.cn
40.72.117.125
443
ECDHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0xC0,0x30
 FS
22 Ciphers, 

174.22 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
 (Secure)
TLSv1.2
0xC0,0x2F
 FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD




ECDHE-RSA-CAMELLIA256-SHA384
 (Weak)
TLSv1.2
0xC0,0x77
 FS

TLS_ECDHE_RSA_WITH_CAMELLIA_256_CBC_SHA384

ECDH
RSA
Camellia(256)
SHA384




ECDHE-RSA-AES256-SHA384
 (Weak)
TLSv1.2
0xC0,0x28
 FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

ECDH
RSA
AES(256)
SHA384




CAMELLIA256-SHA256
 (Weak)
TLSv1.2
0x00,0xC0
 No FS

TLS_RSA_WITH_CAMELLIA_256_CBC_SHA256

RSA
RSA
Camellia(256)
SHA256




AES256-GCM-SHA384
 (Weak)
TLSv1.2
0x00,0x9D
 No FS

TLS_RSA_WITH_AES_256_GCM_SHA384

RSA
RSA
AESGCM(256)
AEAD




AES256-SHA256
 (Weak)
TLSv1.2
0x00,0x3D
 No FS

TLS_RSA_WITH_AES_256_CBC_SHA256

RSA
RSA
AES(256)
SHA256




AES256-CCM8
 (Weak)
TLSv1.2
0xC0,0xA1
 No FS

TLS_RSA_WITH_AES_256_CCM_8

RSA
RSA
AESCCM8(256)
AEAD




AES256-CCM
 (Weak)
TLSv1.2
0xC0,0x9D
 No FS

TLS_RSA_WITH_AES_256_CCM

RSA
RSA
AESCCM(256)
AEAD




ECDHE-RSA-CAMELLIA128-SHA256
 (Weak)
TLSv1.2
0xC0,0x76
 FS

TLS_ECDHE_RSA_WITH_CAMELLIA_128_CBC_SHA256

ECDH
RSA
Camellia(128)
SHA256




ECDHE-RSA-AES128-SHA256
 (Weak)
TLSv1.2
0xC0,0x27
 FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

ECDH
RSA
AES(128)
SHA256




CAMELLIA128-SHA256
 (Weak)
TLSv1.2
0x00,0xBA
 No FS

TLS_RSA_WITH_CAMELLIA_128_CBC_SHA256

RSA
RSA
Camellia(128)
SHA256




AES128-GCM-SHA256
 (Weak)
TLSv1.2
0x00,0x9C
 No FS

TLS_RSA_WITH_AES_128_GCM_SHA256

RSA
RSA
AESGCM(128)
AEAD




AES128-SHA256
 (Weak)
TLSv1.2
0x00,0x3C
 No FS

TLS_RSA_WITH_AES_128_CBC_SHA256

RSA
RSA
AES(128)
SHA256




AES128-CCM8
 (Weak)
TLSv1.2
0xC0,0xA0
 No FS

TLS_RSA_WITH_AES_128_CCM_8

RSA
RSA
AESCCM8(128)
AEAD




AES128-CCM
 (Weak)
TLSv1.2
0xC0,0x9C
 No FS

TLS_RSA_WITH_AES_128_CCM

RSA
RSA
AESCCM(128)
AEAD




ECDHE-RSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x14
 FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

ECDH
RSA
AES(256)
SHA1




ECDHE-RSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x13
 FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

ECDH
RSA
AES(128)
SHA1




CAMELLIA256-SHA
 (Weak)
SSLv3
0x00,0x84
 No FS

TLS_RSA_WITH_CAMELLIA_256_CBC_SHA

RSA
RSA
Camellia(256)
SHA1




AES256-SHA
 (Weak)
SSLv3
0x00,0x35
 No FS

TLS_RSA_WITH_AES_256_CBC_SHA

RSA
RSA
AES(256)
SHA1




CAMELLIA128-SHA
 (Weak)
SSLv3
0x00,0x41
 No FS

TLS_RSA_WITH_CAMELLIA_128_CBC_SHA

RSA
RSA
Camellia(128)
SHA1




AES128-SHA
 (Weak)
SSLv3
0x00,0x2F
 No FS

TLS_RSA_WITH_AES_128_CBC_SHA

RSA
RSA
AES(128)
SHA1


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=da202725-a226-4852-a9d9-877d67072de6

				 
			


Last Result: https://check-your-website.server-daten.de/?q=cn-modelservice-t-api.trafficmanager.cn - 2024-11-29 12:42:40

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

				 
			
<a href="https://check-your-website.server-daten.de/?q=cn-modelservice-t-api.trafficmanager.cn" target="_blank">Check this Site: cn-modelservice-t-api.trafficmanager.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=cn-modelservice-t-api.trafficmanager.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