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


 

 

A

 

Top config

 

Checked:
02.01.2021 15:07:47

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
awslblog.com
A
23.97.73.124
Hong Kong/Central and Western District/Hong Kong (HK) - Microsoft Corporation
No Hostname found
yes
1
0

AAAA

yes


www.awslblog.com

Name Error
yes
1
0
*.awslblog.com
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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 26116, Flags 256






Public Key with Algorithm 8, KeyTag 42351, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.01.2021, 05:00:00 +, Signature-Inception: 02.01.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 31510, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.01.2021, 19:24:21 +, Signature-Inception: 31.12.2020, 19:19:21 +, KeyTag 30909, Signer-Name: com






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






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



Zone: awslblog.com

awslblog.com
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest 7m5KloBVDRIs2/j5Zpf/zog8gmghc1AjxvVg6rpBe6U=






1 RRSIG RR to validate DS RR found






RRSIG-Owner awslblog.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 07.01.2021, 06:13:48 +, Signature-Inception: 31.12.2020, 05:03:48 +, KeyTag 31510, Signer-Name: com






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






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 34505, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 28.01.2021, 23:40:05 +, Signature-Inception: 29.11.2020, 23:40:05 +, KeyTag 2371, Signer-Name: awslblog.com






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






Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest "7m5KloBVDRIs2/j5Zpf/zog8gmghc1AjxvVg6rpBe6U=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone






RRSIG Type 1 validates the A - Result: 23.97.73.124
Validated: RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 6 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






RRSIG Type 16 validates the TXT - Result: v=spf1 mx ~all
Validated: RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






CNAME-Query sends a valid NSEC RR as result with the query name "awslblog.com" equal the NSEC-owner "awslblog.com" and the NextOwner "\000.awslblog.com". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC RR as result with the query name "awslblog.com" equal the NSEC-owner "awslblog.com" and the NextOwner "\000.awslblog.com". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.awslblog.com) sends a valid NSEC RR as result with the query name "_443._tcp.awslblog.com" equal the NSEC-owner "_443._tcp.awslblog.com" and the NextOwner "\000._443._tcp.awslblog.com". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.awslblog.com., Algorithm: 13, 4 Labels, original TTL: 3600 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC RR as result with the query name "awslblog.com" equal the NSEC-owner "awslblog.com" and the NextOwner "\000.awslblog.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI Validated: RRSIG-Owner awslblog.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 03.01.2021, 15:08:05 +, Signature-Inception: 01.01.2021, 13:08:05 +, KeyTag 34505, Signer-Name: awslblog.com






Status: Good. NoData-Proof required and found.



Zone: www.awslblog.com

www.awslblog.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.awslblog.com" and the NextOwner "\000.www.awslblog.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: RRSIG, NSEC

 

3. Name Servers

DomainNameserverNS-IP
www.awslblog.com
  brianna.ns.cloudflare.com

awslblog.com
  brianna.ns.cloudflare.com / 67m35
108.162.192.245
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
172.64.32.245
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
173.245.58.245
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2606:4700:50::adf5:3af5
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c0f5
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:20f5
London/England/United Kingdom (GB) - CloudFLARENET-EU


  duke.ns.cloudflare.com / 67m37
108.162.193.110
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
172.64.33.110
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
173.245.59.110
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2606:4700:58::adf5:3b6e
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c16e
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:216e
London/England/United Kingdom (GB) - CloudFLARENET-EU

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net

 

4. SOA-Entries


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


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


Domain:awslblog.com
Zone-Name:awslblog.com
Primary:brianna.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2036125483
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:12


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


5. Screenshots

Startaddress: https://awslblog.com, address used: https://awslblog.com/, Screenshot created 2021-01-02 15:10:04 +00:0

 

Mobil (412px x 732px)

 

1261 milliseconds

 

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

 

1538 milliseconds

 

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

 

3826 milliseconds

 

Screenshot Desktop - https://awslblog.com/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport404732
content Size4042272

 

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.3, X25519, 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://awslblog.com/
23.97.73.124
301
https://awslblog.com/
Html is minified: 109.46 %
0.403
A
Server: nginx
Date: Sat, 02 Jan 2021 14:08:27 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://awslblog.com/
Strict-Transport-Security: max-age=31536000; includeSubDomains;preload
Expect-CT: max-age=604800, enforce
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src https: data: 'unsafe-eval' 'unsafe-inline';child-src 'none'; object-src 'none';frame-src 'self'

• https://awslblog.com/
23.97.73.124
Inline-JavaScript (∑/total): 36/9471 Inline-CSS (∑/total): 0/0
200

Html is minified: 215.10 %
Other inline scripts (∑/total): 15/9471
5.896
A
Server: nginx
Date: Sat, 02 Jan 2021 14:08:28 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000; includeSubDomains;preload
Expect-CT: max-age=604800, enforce
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src https: data: 'unsafe-eval' 'unsafe-inline';child-src 'none'; object-src 'none';frame-src 'self'
Content-Encoding: gzip

• http://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
23.97.73.124
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.46 %
Other inline scripts (∑/total): 0/0
0.397
A
Visible Content: 301 Moved Permanently nginx
Server: nginx
Date: Sat, 02 Jan 2021 14:08:34 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
Location: https://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Strict-Transport-Security: max-age=31536000; includeSubDomains;preload
Expect-CT: max-age=604800, enforce
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src https: data: 'unsafe-eval' 'unsafe-inline';child-src 'none'; object-src 'none';frame-src 'self'

• https://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 29/8826 Inline-CSS (∑/total): 0/0
404

Html is minified: 216.31 %
Other inline scripts (∑/total): 15/8826
5.340
A
Not Found
Visible Content: menu Thinking Null phonelink more_vert close Thinking Null 菜单 目录 Search home 首页 widgets 分类 keyboard_arrow_down 默认分类 typecho维护 编程(大嘘 C++ JavaScript 科学上网 Linux Ubuncrash 分币OS 网络安全 HTTPS OpenSSL 杂项 数学 setu 状态 秘密 layers 页面 keyboard_arrow_down GPG keys 关于 友链 archive 归档 keyboard_arrow_down 2021 年 1 月 2020 年 12 月 2020 年 11 月 2020 年 10 月 2020 年 9 月 2020 年 8 月 2020 年 7 月 2020 年 5 月 brightness_4 轻语 A good day starts with kernel panic. 美好的一天从kernel panic开始! 查看更多... 最新文章 劲哥讲作文 2021 服务故障通告 USTC Hackergame 2020参赛记录 生成好看的GPG shortID 本站现已正式接入ipv6! 如何使用Dig命令在Linux中查询DNS记录(转载) DoH的滥用方法 为Snapd设置代理 shell 下 urlencode/urldecode 编码/解码的方法 h5ai目录浏览-Firefox浏览器镜像搭建 Windows源代码编译 qBittorrent编译记录 2019ncovmemory dnscrypt-proxy的安装与使用 最近回复 Zya : z wsm不用自签证书( Typecho : 欢迎加入 Typecho 大家族 分类 默认分类 typecho维护 编程(大嘘 C++ JavaScript 科学上网 Linux Ubuncrash 分币OS 网络安全 HTTPS OpenSSL 杂项 数学 setu 状态 秘密 标签 NMSL Latex 114514 Bugs Ubuncrash DNS 浅谈 mysql 葛军 高考 数学 Crash Jvav Telegram tg DoH DoT Status lib FAIL 归档 2021 年 1 月 2020 年 12 月 2020 年 11 月 2020 年 10 月 2020 年 9 月 2020 年 8 月 2020 年 7 月 2020 年 5 月 链接 FlyingSky's Blog 翰林的小站 萌博 浅笑 blog 查看更多 网站统计 文章总数: 31 篇 评论总数: 7 条 总访问量: 2,226 404 - 页面没找到 你想查看的页面已被转移或删除了 © 2021 Thinking Null . Powered by Typecho & MDr . 一言获取中... 博客已上线 . 萌ICP备20209810 keyboard_arrow_up
Server: nginx
Date: Sat, 02 Jan 2021 14:08:41 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000; includeSubDomains;preload
Content-Encoding: gzip

• https://23.97.73.124/
23.97.73.124
Inline-JavaScript (∑/total): 36/9471 Inline-CSS (∑/total): 0/0
200

Html is minified: 215.10 %
Other inline scripts (∑/total): 15/9471
5.683
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx
Date: Sat, 02 Jan 2021 14:08:35 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000; includeSubDomains;preload
Expect-CT: max-age=604800, enforce
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src https: data: 'unsafe-eval' 'unsafe-inline';child-src 'none'; object-src 'none';frame-src 'self'
Content-Encoding: gzip

 

7. Comments


1. General Results, most used to calculate the result

Aname "awslblog.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: awslblog.com 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: awslblog.com has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 31536000 seconds = 365 days
AGood: HSTS has includeSubdomains - directive
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload 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.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://awslblog.com/ 23.97.73.124
301
https://awslblog.com/
Correct redirect http - https with the same domain name
Nhttps://23.97.73.124/ 23.97.73.124
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain awslblog.com, 1 ip addresses, 1 different http results.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: brianna.ns.cloudflare.com, duke.ns.cloudflare.com, 2 Name Servers included in Delegation: brianna.ns.cloudflare.com, duke.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: brianna.ns.cloudflare.com, duke.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: brianna.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: brianna.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: brianna.ns.cloudflare.com.
AGood: Consistency 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. Ordered list of name servers: brianna.ns.cloudflare.com, duke.ns.cloudflare.com
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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: cloudflare.com
AGood: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US
AInfo: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 172., 173., 3 different subnets (first two Bytes): 108.162., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.245.58., 173.245.59.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
Nameserver doesn't pass all EDNS-Checks: brianna.ns.cloudflare.com: 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.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://awslblog.com/ 23.97.73.124
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://23.97.73.124/ 23.97.73.124
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://awslblog.com/ 23.97.73.124
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://23.97.73.124/ 23.97.73.124
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.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AGood: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
https://awslblog.com/ 23.97.73.124
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.: 21 script elements without defer/async.
https://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404

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.: 14 script elements without defer/async.
https://23.97.73.124/ 23.97.73.124
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.: 21 script elements without defer/async.
Warning: CSS / JavaScript found without Compression. Compress these ressources, gzip, deflate, br are checked. 3 external CSS / JavaScript files without GZip found - 74 with GZip, 77 complete
AGood: All images with internal compression not compressed. Some Images (.png, .jpg, .jpeg, .webp, .gif) are already compressed, so an additional compression isn't helpful. 12 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. 6 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 44 with Cache-Control max-age too short (minimum 7 days), 27 with Cache-Control long enough, 77 complete.
AGood: All images are sent with a long Cache-Control header (minimum 7 days). So the browser can reuse these files, no download is required. 14 image files with long Cache-Control max-age found
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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.: 14 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
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
http://awslblog.com/ 23.97.73.124
301

Warning: HSTS header sent via http has no effect
https://awslblog.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
5.340 seconds
Warning: 404 needs more then one second
ADuration: 144050 milliseconds, 144.050 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
awslblog.com
23.97.73.124
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
awslblog.com
23.97.73.124
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
http/2 via ALPN supported 
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
No SNI required - domain included in main certificate
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=awsl.tech


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


awslblog.com
awslblog.com
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok

awslblog.com
awslblog.com
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=awsl.tech


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


23.97.73.124
23.97.73.124
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
supported
ok

23.97.73.124
23.97.73.124
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
supported
ok
http/2 via ALPN supported 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=awsl.tech


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

 

9. Certificates

1.
1.
CN=awsl.tech
01.01.2021
01.04.2021
1414 days expired
*.awneed.icu, *.awsl.blog, *.awsl.tech, *.awsl.wtf, *.awslblog.com, *.plashspeed.tech, awsl.blog, awsl.tech, awsl.wtf, awslblog.com, plashspeed.tech - 11 entries
1.
1.
CN=awsl.tech
01.01.2021

01.04.2021
1414 days expired


*.awneed.icu, *.awsl.blog, *.awsl.tech, *.awsl.wtf, *.awslblog.com, *.plashspeed.tech, awsl.blog, awsl.tech, awsl.wtf, awslblog.com, plashspeed.tech - 11 entries

KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:03D57EBAFF9F8AE817F13A513959319116AA
Thumbprint:850C7067D7D9D6636EAFD2A0EF36F9D494063526
SHA256 / Certificate:xg+Q5yQCTRA7Ticr9hlK/96VZHM7ZHRSLVHLCGB8AuU=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):c36b1e475c3f68a83a273da94633c7d04262fdd98944b89271fddcd2a9b21d04
SHA256 hex / Subject Public Key Information (SPKI):c36b1e475c3f68a83a273da94633c7d04262fdd98944b89271fddcd2a9b21d04
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:yes
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=R3, O=Let's Encrypt, C=US
07.10.2020
29.09.2021
1233 days expired


2.
CN=R3, O=Let's Encrypt, C=US
07.10.2020

29.09.2021
1233 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:400175048314A4C8218C84A90C16CDDF
Thumbprint:48504E974C0DAC5B5CD476C8202274B24C8C7172
SHA256 / Certificate:cwwb3NhfV85dwLunM+XxulqSWyp3HWQKJvekVCJNrTs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
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), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1232 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1232 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:




 

10. Last Certificates - Certificate Transparency Log Check

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

Small Code Update - wait one minute

 

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

Small Code Update - wait one minute

 

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: brianna.ns.cloudflare.com, duke.ns.cloudflare.com

 

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
brianna.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
3
duke.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
4
brianna.ns.cloudflare.com: 108.162.192.245, 172.64.32.245, 173.245.58.245
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
brianna.ns.cloudflare.com: 2606:4700:50::adf5:3af5, 2803:f800:50::6ca2:c0f5, 2a06:98c1:50::ac40:20f5
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
duke.ns.cloudflare.com: 108.162.193.110, 172.64.33.110, 173.245.59.110
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
duke.ns.cloudflare.com: 2606:4700:58::adf5:3b6e, 2803:f800:50::6ca2:c16e, 2a06:98c1:50::ac40:216e
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
awslblog.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
awslblog.com
v=spf1 mx ~all
ok
1
0
_acme-challenge.awslblog.com


1
0
_acme-challenge.awslblog.com.awslblog.com

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

DomainIPPortDescriptionResultAnswer
awslblog.com
23.97.73.124
21
FTP



awslblog.com
23.97.73.124
21
FTP



awslblog.com
23.97.73.124
22
SSH



awslblog.com
23.97.73.124
22
SSH



awslblog.com
23.97.73.124
25
SMTP



awslblog.com
23.97.73.124
25
SMTP



awslblog.com
23.97.73.124
53
DNS



awslblog.com
23.97.73.124
53
DNS



awslblog.com
23.97.73.124
110
POP3



awslblog.com
23.97.73.124
110
POP3



awslblog.com
23.97.73.124
143
IMAP



awslblog.com
23.97.73.124
143
IMAP



awslblog.com
23.97.73.124
465
SMTP (encrypted)



awslblog.com
23.97.73.124
465
SMTP (encrypted)



awslblog.com
23.97.73.124
587
SMTP (encrypted, submission)



awslblog.com
23.97.73.124
587
SMTP (encrypted, submission)



awslblog.com
23.97.73.124
993
IMAP (encrypted)



awslblog.com
23.97.73.124
993
IMAP (encrypted)



awslblog.com
23.97.73.124
995
POP3 (encrypted)



awslblog.com
23.97.73.124
995
POP3 (encrypted)



awslblog.com
23.97.73.124
1433
MS SQL



awslblog.com
23.97.73.124
1433
MS SQL



awslblog.com
23.97.73.124
2082
cPanel (http)



awslblog.com
23.97.73.124
2082
cPanel (http)



awslblog.com
23.97.73.124
2083
cPanel (https)



awslblog.com
23.97.73.124
2083
cPanel (https)



awslblog.com
23.97.73.124
2086
WHM (http)



awslblog.com
23.97.73.124
2086
WHM (http)



awslblog.com
23.97.73.124
2087
WHM (https)



awslblog.com
23.97.73.124
2087
WHM (https)



awslblog.com
23.97.73.124
2089
cPanel Licensing



awslblog.com
23.97.73.124
2089
cPanel Licensing



awslblog.com
23.97.73.124
2095
cPanel Webmail (http)



awslblog.com
23.97.73.124
2095
cPanel Webmail (http)



awslblog.com
23.97.73.124
2096
cPanel Webmail (https)



awslblog.com
23.97.73.124
2096
cPanel Webmail (https)



awslblog.com
23.97.73.124
2222
DirectAdmin (http)



awslblog.com
23.97.73.124
2222
DirectAdmin (http)



awslblog.com
23.97.73.124
2222
DirectAdmin (https)



awslblog.com
23.97.73.124
2222
DirectAdmin (https)



awslblog.com
23.97.73.124
3306
mySql



awslblog.com
23.97.73.124
3306
mySql



awslblog.com
23.97.73.124
5224
Plesk Licensing



awslblog.com
23.97.73.124
5224
Plesk Licensing



awslblog.com
23.97.73.124
5432
PostgreSQL



awslblog.com
23.97.73.124
5432
PostgreSQL



awslblog.com
23.97.73.124
8080
Ookla Speedtest (http)



awslblog.com
23.97.73.124
8080
Ookla Speedtest (http)



awslblog.com
23.97.73.124
8080
Ookla Speedtest (https)



awslblog.com
23.97.73.124
8080
Ookla Speedtest (https)



awslblog.com
23.97.73.124
8083
VestaCP http



awslblog.com
23.97.73.124
8083
VestaCP http



awslblog.com
23.97.73.124
8083
VestaCP https



awslblog.com
23.97.73.124
8083
VestaCP https



awslblog.com
23.97.73.124
8443
Plesk Administration (https)



awslblog.com
23.97.73.124
8443
Plesk Administration (https)



awslblog.com
23.97.73.124
8447
Plesk Installer + Updates



awslblog.com
23.97.73.124
8447
Plesk Installer + Updates



awslblog.com
23.97.73.124
8880
Plesk Administration (http)



awslblog.com
23.97.73.124
8880
Plesk Administration (http)



awslblog.com
23.97.73.124
10000
Webmin (http)



awslblog.com
23.97.73.124
10000
Webmin (http)



awslblog.com
23.97.73.124
10000
Webmin (https)



awslblog.com
23.97.73.124
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=af832307-1d50-4b00-bb04-0408af699ec7

 

Last Result: https://check-your-website.server-daten.de/?q=awslblog.com - 2021-01-02 15:07:47

 

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

 

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