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

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

 

A

 

Top config

 

Checked:
24.07.2023 23:41:01

 

Older results

 

F - 21.07.2023 23:44:30

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
yartys.no
A

yes
1
0

AAAA
2a07:40:40:a:0:52a2:ef1b:994
Sandnes/Rogaland/Norway (NO) - IP Group AS

yes


www.yartys.no
A

yes
1
0

AAAA
2a07:40:40:a:0:52a2:ef1b:994
Sandnes/Rogaland/Norway (NO) - IP Group AS

yes


*.yartys.no
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 11019, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






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

no
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 38032, DigestType 2 and Digest bTdNdp0eQ4ixpUmm2i99iTcdtquqU9IO7HCETbQGLlE=






1 RRSIG RR to validate DS RR found






RRSIG-Owner no., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.08.2023, 21:00:00 +, Signature-Inception: 24.07.2023, 20:00:00 +, KeyTag 11019, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 37317, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner no., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 06.08.2023, 19:43:47 +, Signature-Inception: 23.07.2023, 19:02:37 +, KeyTag 38032, Signer-Name: no






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






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



Zone: yartys.no

yartys.no
2 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 56034, DigestType 2 and Digest xUYXQdQuK+3AmoiD4x5THVmkzZp2ezHOTRMYe4UqvaE=






DS with Algorithm 13, KeyTag 56034, DigestType 4 and Digest rA32QfcfjKMP5PY5nyc9tt+6KsEPViFAi+FxlclmnzOGXdgVkDguQohQoG/ydC9x






1 RRSIG RR to validate DS RR found






RRSIG-Owner yartys.no., Algorithm: 13, 2 Labels, original TTL: 7200 sec, Signature-expiration: 06.08.2023, 02:55:22 +, Signature-Inception: 24.07.2023, 03:05:13 +, KeyTag 37317, Signer-Name: no






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 28878, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner yartys.no., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






RRSIG-Owner yartys.no., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 56034, Signer-Name: yartys.no






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






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 56034, DigestType 2 and Digest "xUYXQdQuK+3AmoiD4x5THVmkzZp2ezHOTRMYe4UqvaE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 56034, DigestType 4 and Digest "rA32QfcfjKMP5PY5nyc9tt+6KsEPViFAi+FxlclmnzOGXdgVkDguQohQoG/ydC9x" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone






RRSIG Type 16 validates the TXT - Result: v=spf1 include:_spf.protonmail.ch mx ~all protonmail-verification=e316c9d19bb1d5c9f1c7f2ac70125ce9c7d0a94f
Validated: RRSIG-Owner yartys.no., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






RRSIG Type 28 validates the AAAA - Result: 2A07:0040:0040:000A:0000:52A2:EF1B:0994
Validated: RRSIG-Owner yartys.no., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






A-Query sends a valid NSEC3 RR as result with the hashed query name "1n14gc9k7t4oj39kdce3jvumaa7ruahb" equal the hashed NSEC3-owner "1n14gc9k7t4oj39kdce3jvumaa7ruahb" and the hashed NextOwner "ckrsj320vfgd86r1l26cql3c5rfjkj06". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1n14gc9k7t4oj39kdce3jvumaa7ruahb.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "1n14gc9k7t4oj39kdce3jvumaa7ruahb" equal the hashed NSEC3-owner "1n14gc9k7t4oj39kdce3jvumaa7ruahb" and the hashed NextOwner "ckrsj320vfgd86r1l26cql3c5rfjkj06". 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: NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1n14gc9k7t4oj39kdce3jvumaa7ruahb.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.yartys.no) sends a valid NSEC3 RR as result with the hashed owner name "1n14gc9k7t4oj39kdce3jvumaa7ruahb" (unhashed: yartys.no). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "b5kobtm774t9m2gmektsv2ke21nt480d" (unhashed: _tcp.yartys.no) with the owner "1n14gc9k7t4oj39kdce3jvumaa7ruahb" and the NextOwner "ckrsj320vfgd86r1l26cql3c5rfjkj06". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1n14gc9k7t4oj39kdce3jvumaa7ruahb.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "ldm3jdod707ac9lnbqr8g2lntimvjg2i" (unhashed: *.yartys.no) with the owner "ghva75dptb9ej1s2bvaqjshbb3oha72u" and the NextOwner "t5nqjedcsrhh1e0hkbnptqmb3ppefpof". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner ghva75dptb9ej1s2bvaqjshbb3oha72u.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "1n14gc9k7t4oj39kdce3jvumaa7ruahb" equal the hashed NSEC3-owner "1n14gc9k7t4oj39kdce3jvumaa7ruahb" and the hashed NextOwner "ckrsj320vfgd86r1l26cql3c5rfjkj06". 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: NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 1n14gc9k7t4oj39kdce3jvumaa7ruahb.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.



Zone: www.yartys.no

www.yartys.no
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 "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" between the hashed NSEC3-owner "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" and the hashed NextOwner "eaqq0am7pd7u6vop38fg57p295dljl78". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






RRSIG Type 28 validates the AAAA - Result: 2A07:0040:0040:000A:0000:52A2:EF1B:0994
Validated: RRSIG-Owner www.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






A-Query sends a valid NSEC3 RR as result with the hashed query name "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" equal the hashed NSEC3-owner "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" and the hashed NextOwner "eaqq0am7pd7u6vop38fg57p295dljl78". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" equal the hashed NSEC3-owner "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" and the hashed NextOwner "eaqq0am7pd7u6vop38fg57p295dljl78". 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: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" equal the hashed NSEC3-owner "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" and the hashed NextOwner "eaqq0am7pd7u6vop38fg57p295dljl78". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.yartys.no) sends a valid NSEC3 RR as result with the hashed owner name "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" (unhashed: www.yartys.no). So that's the Closest Encloser of the query name.
Bitmap: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "mchu1lvv8k5kt3dau9i38miegk4uj0v3" (unhashed: _tcp.www.yartys.no) with the owner "ghva75dptb9ej1s2bvaqjshbb3oha72u" and the NextOwner "t5nqjedcsrhh1e0hkbnptqmb3ppefpof". So that NSEC3 confirms the not-existence of the Next Closer Name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "ptj578n4fo02c8f20bamjhic47ondbso" (unhashed: *.www.yartys.no) with the owner "ghva75dptb9ej1s2bvaqjshbb3oha72u" and the NextOwner "t5nqjedcsrhh1e0hkbnptqmb3ppefpof". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner ghva75dptb9ej1s2bvaqjshbb3oha72u.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" equal the hashed NSEC3-owner "dc24n9ntjccp7jjnvn87v1m5hggqdmsv" and the hashed NextOwner "eaqq0am7pd7u6vop38fg57p295dljl78". 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: AAAA, RRSIG Validated: RRSIG-Owner dc24n9ntjccp7jjnvn87v1m5hggqdmsv.yartys.no., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2023, 21:17:13 +, Signature-Inception: 19.07.2023, 21:17:13 +, KeyTag 28878, Signer-Name: yartys.no






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.yartys.no
•  ns1.hyp.net / ams.nl
•
yartys.no
•  ns1.hyp.net / ams.nl
151.249.124.1
Oslo/Oslo County/Norway (NO) - Domeneshop		•

• 
2a01:5b40:ac1::1
Oslo/Oslo County/Norway (NO) - Domeneshop AS		•

•  ns2.hyp.net / reg-fam1_customer10
192.174.68.10
Vienna/Austria (AT) - ipcom GmbH		•

• 
2001:67c:1bc::10
Salzburg/Austria (AT) - IPCom-NET Anycast		•

•  ns3.hyp.net / par.fr
151.249.126.3
Oslo/Oslo County/Norway (NO) - hyp.net anycast		•

• 
2a01:5b40:ac3::1
Oslo/Oslo County/Norway (NO) - Domeneshop		•
no
•  charm.norid.no


•  i.nic.no / s2.cmx
•

•  njet.norid.no / TLD_Host2.Frankfurt_Node1
•

•  not.norid.no / TLD_Host2.Frankfurt_Node1
•

•  x.nic.no
•

•  y.nic.no / y.nic.no
•

•  z.nic.no / z.nic.no
•

 

4. SOA-Entries


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


Domain:no
Zone-Name:no
Primary:charm.norid.no
Mail:hostmaster.norid.no
Serial:2023072472
Refresh:7200
Retry:1800
Expire:2419200
TTL:7200
num Entries:6


Domain:yartys.no
Zone-Name:yartys.no
Primary:ns1.hyp.net
Mail:hostmaster.domeneshop.no
Serial:1689805033
Refresh:21600
Retry:3600
Expire:1209600
TTL:3600
num Entries:6


Domain:www.yartys.no
Zone-Name:yartys.no
Primary:ns1.hyp.net
Mail:hostmaster.domeneshop.no
Serial:1689805033
Refresh:21600
Retry:3600
Expire:1209600
TTL:3600
num Entries:1


5. Screenshots

Startaddress: https://yartys.no/, address used: https://yartys.no/, Screenshot created 2023-07-24 23:43:38 +00:0

 

Mobil (412px x 732px)

 

158 milliseconds

 

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

 

159 milliseconds

 

Screenshot mobile landscape - https://yartys.no/
Screen (1280px x 1680px)

 

292 milliseconds

 

Screenshot Desktop - https://yartys.no/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://yartys.no/
2a07:40:40:a:0:52a2:ef1b:994
301
https://yartys.no/
Html is minified: 100.00 %
0.063
A
Date: Mon, 24 Jul 2023 21:41:46 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://yartys.no/
Content-Length: 301
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.yartys.no/
2a07:40:40:a:0:52a2:ef1b:994
301
https://www.yartys.no
Html is minified: 100.00 %
0.073
A
Date: Mon, 24 Jul 2023 21:41:46 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://www.yartys.no
Content-Length: 308
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://www.yartys.no/
2a07:40:40:a:0:52a2:ef1b:994
301
https://yartys.no/
Html is minified: 100.00 %
2.294
A
Date: Mon, 24 Jul 2023 21:41:46 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=31536000; includeSubDomains
Location: https://yartys.no/
Content-Length: 306
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://www.yartys.no

301
https://yartys.no/
Html is minified: 100.00 %
2.363
A
Date: Mon, 24 Jul 2023 21:41:56 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=31536000; includeSubDomains
Location: https://yartys.no/
Content-Length: 306
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://yartys.no/
2a07:40:40:a:0:52a2:ef1b:994
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		200

Html is minified: 110.00 %
Other inline scripts (∑/total): 0/0		2.294
A
small visible content (num chars: 17)
Nothing here yet!
Date: Mon, 24 Jul 2023 21:41:49 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=31536000; includeSubDomains
Last-Modified: Mon, 24 Jul 2023 19:56:42 GMT
ETag: "4d-6014103731680-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 81
Connection: close
Content-Type: text/html

• http://yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a07:40:40:a:0:52a2:ef1b:994
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		0.077
A
Visible Content: Moved Permanently The document has moved here . Apache/2.4.52 (Ubuntu) Server at yartys.no Port 80
Date: Mon, 24 Jul 2023 21:41:53 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 370
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a07:40:40:a:0:52a2:ef1b:994
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		301
https://www.yartys.no.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		0.070
A
Visible Content: Moved Permanently The document has moved here . Apache/2.4.52 (Ubuntu) Server at www.yartys.no Port 80
Date: Mon, 24 Jul 2023 21:41:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://www.yartys.no.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 377
Connection: close
Content-Type: text/html; charset=iso-8859-1

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

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

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		2.384
A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache/2.4.52 (Ubuntu) Server at yartys.no Port 443
Date: Mon, 24 Jul 2023 21:41:59 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Length: 272
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://www.yartys.no.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-1


0.017
R
NameResolutionFailure - The remote name could not be resolved: 'www.yartys.no.well-known'
Visible Content:

• https://[2a07:0040:0040:000a:0000:52a2:ef1b:0994]/
2a07:40:40:a:0:52a2:ef1b:994
301
https://yartys.no/
Html is minified: 100.00 %
2.337
N
Certificate error: RemoteCertificateNameMismatch
Date: Mon, 24 Jul 2023 21:41:53 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=31536000; includeSubDomains
Location: https://yartys.no/
Content-Length: 321
Connection: close
Content-Type: text/html; charset=iso-8859-1

 

7. Comments


1. General Results, most used to calculate the result

Aname "yartys.no" is domain, public suffix is ".no", top-level-domain is ".no", top-level-domain-type is "country-code", Country is Norway, tld-manager is "UNINETT Norid A/S", num .no-domains preloaded: 429 (complete: 228216)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: www.yartys.no has only one ip address.
Warning: Only one ip address found: yartys.no has only one ip address.
AGood: No asked Authoritative Name Server had a timeout
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.
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
https://yartys.no/ 2a07:40:40:a:0:52a2:ef1b:994


Url with incomplete Content-Type - header - missing charset
Ahttp://yartys.no/ 2a07:40:40:a:0:52a2:ef1b:994
301
https://yartys.no/
Correct redirect http - https with the same domain name
Nhttps://[2a07:0040:0040:000a:0000:52a2:ef1b:0994]/ 2a07:40:40:a:0:52a2:ef1b:994
301
https://yartys.no/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Rhttp://www.yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a07:40:40:a:0:52a2:ef1b:994
301
https://www.yartys.no.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Redirect to not existing domain
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 www.yartys.no, 1 ip addresses, 1 different http results.
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 yartys.no, 1 ip addresses, 1 different http results.
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.yartys.no

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

Fyartys.no 2a07:40:40:a:0:52a2:ef1b:994
Content-Security-Policy
Critical: Missing Header:
Fyartys.no 2a07:40:40:a:0:52a2:ef1b:994
X-Content-Type-Options
Critical: Missing Header:
Fyartys.no 2a07:40:40:a:0:52a2:ef1b:994
Referrer-Policy
Critical: Missing Header:
Fyartys.no 2a07:40:40:a:0:52a2:ef1b:994
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.hyp.net (151.249.124.1, 2a01:5b40:ac1::1), ns2.hyp.net (192.174.68.10, 2001:67c:1bc::10), ns3.hyp.net (151.249.126.3, 2a01:5b40:ac3::1)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.hyp.net, ns2.hyp.net, ns3.hyp.net, 3 Name Servers included in Delegation: ns1.hyp.net, ns2.hyp.net, ns3.hyp.net, 3 Name Servers included in 1 Zone definitions: ns1.hyp.net, ns2.hyp.net, ns3.hyp.net, 1 Name Servers listed in SOA.Primary: ns1.hyp.net.
AGood: Only one SOA.Primary Name Server found.: ns1.hyp.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.hyp.net.
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: ns1.hyp.net, ns2.hyp.net, ns3.hyp.net
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: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 Name Servers, 1 Top Level Domain: net
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: hyp.net
AGood: Name servers with different Country locations found: 3 Name Servers, 2 Countries: AT, NO
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 151., 192., 2 different subnets (first two Bytes): 151.249., 192.174., 3 different subnets (first three Bytes): 151.249.124., 151.249.126., 192.174.68.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2a01:, 2 different subnets (first two blocks): 2001:067c:, 2a01:5b40:, 3 different subnets (first three blocks): 2001:067c:01bc:, 2a01:5b40:0ac1:, 2a01:5b40:0ac3:, 3 different subnets (first four blocks): 2001:067c:01bc:0000:, 2a01:5b40:0ac1:0000:, 2a01:5b40:0ac3:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: charm.norid.no: 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: ns1.hyp.net: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: ok (ams.nl). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.hyp.net / 151.249.124.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ams.nl). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.hyp.net / 2a01:5b40:ac1::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (cph.dk). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.hyp.net / 151.249.126.3: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (par.fr). COOKIE: fatal timeout. 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

https://www.yartys.no.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-1

Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
https://yartys.no/ 2a07:40:40:a:0:52a2:ef1b:994
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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://yartys.no/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
2.384 seconds
Warning: 404 needs more then one second
ADuration: 168146 milliseconds, 168.146 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=yartys.no


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


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


www.yartys.no
www.yartys.no
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.yartys.no
www.yartys.no
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=yartys.no


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


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


www.yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
No SNI required - domain included in main certificate 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=yartys.no


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


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


yartys.no
yartys.no
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

yartys.no
yartys.no
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=yartys.no


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


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


[2a07:0040:0040:000a:0000:52a2:ef1b:0994]
2a07:40:40:a:0:52a2:ef1b:994
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

[2a07:0040:0040:000a:0000:52a2:ef1b:0994]
2a07:40:40:a:0:52a2:ef1b:994
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=yartys.no


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


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

 

9. Certificates

1.
1.
CN=yartys.no
21.07.2023
19.10.2023
411 days expired		www.yartys.no, yartys.no - 2 entries
1.
1.
CN=yartys.no
21.07.2023

19.10.2023
411 days expired


www.yartys.no, yartys.no - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:032B0A3999F77CFDD59FD784648F0C6474B7
Thumbprint:E317EE9EE0BE06990A5D6D03AFD48DD2A5A38FD2
SHA256 / Certificate:oql8FOPvFiL4mwvMkobCPE9KM/9izr2Mxy8T9KFWRok=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):122cb6d09776e77e864be3b335a95b63be0f472711be760c6ec446a19d20391c
SHA256 hex / Subject Public Key Information (SPKI):122cb6d09776e77e864be3b335a95b63be0f472711be760c6ec446a19d20391c (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.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=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 286 days

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

15.09.2025
expires in 286 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
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: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 3835 days

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

04.06.2035
expires in 3835 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:




 

10. Last Certificates - Certificate Transparency Log Check

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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
5561856769
leaf cert		CN=R3, O=Let's Encrypt, C=US
2023-07-21 19:54:19
2023-10-19 19:54:18
www.yartys.no, yartys.no - 2 entries


 

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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9975361505
precert		CN=R3, O=Let's Encrypt, C=US
2023-07-21 17:54:19
2023-10-19 17:54:18
www.yartys.no, yartys.no
2 entries


 

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.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.hyp.net, ns2.hyp.net, ns3.hyp.net

 

QNr.DomainTypeNS used
1
net
NS
l.root-servers.net (2001:500:9f::42)

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
ns1.hyp.net: 151.249.124.1, 2a01:5b40:ac1::1
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.hyp.net
192.174.68.10, 2001:67c:1bc::10

Answer: ns3.hyp.net
151.249.126.3, 2a01:5b40:ac3::1

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.yartys.no
0

no CAA entry found
1
0
yartys.no
0

no CAA entry found
1
0
no
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
yartys.no
protonmail-verification=e316c9d19bb1d5c9f1c7f2ac70125ce9c7d0a94f
ok
1
0
yartys.no
v=spf1 include:_spf.protonmail.ch mx ~all
ok
1
0
www.yartys.no

ok
1
0
_acme-challenge.yartys.no

Name Error - The domain name does not exist
1
0
_acme-challenge.www.yartys.no

Name Error - The domain name does not exist
1
0
_acme-challenge.yartys.no.yartys.no

Name Error - The domain name does not exist
1
0
_acme-challenge.www.yartys.no.yartys.no

Name Error - The domain name does not exist
1
0
_acme-challenge.www.yartys.no.www.yartys.no

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

yartys.no
10
mail.protonmail.ch
02ok

A


185.70.42.128
03ok

A


185.205.70.128
03ok

A


176.119.200.128
03ok

CNAME


00ok
MX

yartys.no
20
mailsec.protonmail.ch
02ok

A


185.70.42.129
03ok

A


176.119.200.129
03ok

A


185.205.70.129
03ok

CNAME


00ok
_dmarc
TXT
_dmarc.yartys.no

v=DMARC1; p=reject
ok

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
5 Ciphers35.17 sec
0 without, 5 FS
100.00 %
www.yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
5 Ciphers35.03 sec
0 without, 5 FS
100.00 %
Complete

2
10 Ciphers
5.00 Ciphers/Check		70.20 sec35.10 sec/Check
0 without, 10 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
5 Ciphers, 

35.17 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
RSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0xC0,0x30
 FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




DHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0x00,0x9F
 FS

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

DH
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




DHE-RSA-AES128-GCM-SHA256
 (Secure)
TLSv1.2
0x00,0x9E
 FS

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

DH
RSA
AESGCM(128)
AEAD

www.yartys.no
2a07:40:40:a:0:52a2:ef1b:994
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
5 Ciphers, 

35.03 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
RSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0xC0,0x30
 FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




DHE-RSA-AES256-GCM-SHA384
 (Secure)
TLSv1.2
0x00,0x9F
 FS

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

DH
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




DHE-RSA-AES128-GCM-SHA256
 (Secure)
TLSv1.2
0x00,0x9E
 FS

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

DH
RSA
AESGCM(128)
AEAD


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=9deaee68-a3b4-4fcb-a8e5-319e047157d4

				 
			


Last Result: https://check-your-website.server-daten.de/?q=yartys.no - 2023-07-24 23:41:01

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

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

				 
			

				 
			



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